Comment by dgellow
2 years ago
They got lot of push back because what the core devs were describing Vlang to be was technically close to impossible, and their implementation was missing lot of properties they were advertising. If you would look at their sources or try out V when they released it you would have seen how outrageous their claims were.
There were no close to impossible/missing features.
Last time I looked was beginning of 2022, and I read their stdlib implementation and tried the compiler. They advertised their non-GC solution, “auto free”, but it literally didn’t work, your program would just leak. And if you actually look at what they meant by “autofree”, it is a reference counting GC. They advertised Rust memory management ergonomics but without relying on linear types? Their way to do system calls was by running commands in shells.
Unless things changed drastically V lang, as described by their documentation, is a vapor ware.
autofree is not reference counting, and it's marked as "not production ready yet" on the website.
You're saying that when Volt and V were first announced, there were no advertised features that were missing?
What about GC-less autofree?
I'm still waiting for that CS breakthrough to happen - Rust guys will be so mad they spent their time writing lifetime annotations for the borrow checker :)
You can look up vlang.io on web archive and see that it never said GC-less autofree. It actually explicitly said that RC/GC are used for stuff that can't be freed during compile time.
18 replies →