1,578 karma · joined November 15, 2016
This doesn't happen, we have V web services running for months without leaks.
But since there were several responses with this message, I'll make sure valgrind reports 0 :)
There's no ownership in V and it's not planned.
But it does borrow immutability, sum types, some elements of memory handling.
V is much closer to Go, about 80% close I'd say:
There are now V contributors who used to troll V back in the day.
He was really persistent with his attacks, even received a warning from dang.
I found it really surprising, because before the release he wrote:
> Wow, that's incredibly fast. Self-hosted in 2 weeks? Hot code reloading? This is everything I plan to do with Zig, but apparently done already. How did you do it so quickly?
https://github.com/vlang/v/discussions/7610
Wishing V to die and making false accusations is not "constructive criticism".
There will be a blog post next week.
Reporting these issues wouldn't take a month, like the article, and they'd be fixed right away, as they were after the article was published.
This is completely irrelevant. Each V program uses an extra 800 bytes.
If you look at what actual performance and low resource usage V brings to the table, you'll see it's not a problem at all.
I'll make a detailed post about this next week.
I'll publish a big blog post about this. It will debunk all these "V is a scam" articles.
Basically V appeared out of nowhere and got popular very fast. It took a lot of shortcuts: it was self hosted on release, GitHub started supporting it 1 month after the release, it had hot code reloading, fast compilation (v self is <1s [0]) and so on.
People developing other languages and their communities didn't like it, and decided to attack it.
There were 2 strategies: making completely false statements (like claiming that the V compiler has a dependency on glfw, so the no dependency claim is false, and claiming that V programs use libc, system's only official API, therefore again the no dependency claim is false) and nitpicking over bugs that are inevitable in a 0.1 language, and sometimes complaining that features explicitly marked as [wip] are not ready yet. One of the common questions I saw is "why release it if it's not ready". While that's the whole point of open source. I got lots of help from 500+ contributors and got to this point a lot faster.
Then there was also a misunderstanding with the "preview" release one week before the source code was released, and many thought V was going to be closed source. Over this week unfinished features were not marked as [wip]. They were marked so after the open source release, and now there're no [wip] features on the website. Everything listed there is working in latest V.
V doesn't free memory when building V for performance reasons.
A compiler is a perfect example of an app where freeing memory is totally fine on exit, by the OS.
Fortunately V is efficient and doesn't result in gigabytes of RAM used when compiling large bases of code (V itself is about 110k loc + 100k of vlib).
Once there are code bases that require gigabytes of RAM, we'll add an option to free it as it goes.
I don't think any other language has them merged.
There were issues later with the 3 states (Ok, Error, none) instead of a simple binary state.
Since the `or {}` block handles the "not Ok", developers had to check whether it was an Error or a `none`, it's not pretty.
Since it was another anonymous attack, it's not going to be updated and will stay like this for years.
And the issues discussed are questionable at best. Half the article is about a type checker bug, which was a 3 line fix.
Then false claims like being able to modify array.len.
There's also Gitly, which we're launching next week.
To be fair, "in one hour" was updated to "over a weekend" on the home page. I just did the same in README.md.
The language has definitely grown as you can see by the size of the docs.
But it's definitely not bigger than Go, and that one has always been famous in the industry for being simple.
The best thing is that V is always going to stay small. No constant changes and new complexity (looking at you, C#).
We know it's not a big deal, we have lots of valgrind tests running on CI. And we have V web services running for months and not leaking memory.