# The V Programming Language

**URL:** <https://forum.devtalk.com/t/the-v-programming-language/8649>\
**Category:** General Dev Chat\
**Tags:** v, programming-languages\
**Created:** [9 April 2021 13:22 UTC](https://forum.devtalk.com/t/the-v-programming-language/8649 "2021-04-09T13:22:39Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DevotionGeo](https://forum.devtalk.com/user_avatar/forum.devtalk.com/devotiongeo/32/1140_2.png) [@DevotionGeo](https://forum.devtalk.com/u/DevotionGeo)\
**Post date:** [9 April 2021 18:57 UTC](https://forum.devtalk.com/t/the-v-programming-language/8649/8 "2021-04-09T18:57:46Z")

</div>

Looks like the ~90-100% `autofree` and then reference counting, is a good memory management, and is very practical too, as proved by [translating DOOM from C to V and building it in 0.7 seconds](https://github.com/vlang/doom), and the [demo](https://youtu.be/gmB8ea8uLsM) showing [Ved editor](https://github.com/vlang/ved) compiled with `--autofree`, running with 0 memory leaks.

And the good thing about `autofree` is that "The developer doesn’t need to change anything in their code. “It just works” ".

---

_[View the full topic](https://forum.devtalk.com/t/the-v-programming-language/8649)._