> Yeah basically complaining that WIP features explicitly marked as WIP are not ready ...As far as I know, several of these features were not marked as WIP when this article was posted. Additionally, no features were marked at all close to the article's posting. From the article:
> This article was posted on 2019-06-23. Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear.
One if its criticisms is the claim on memory management. Here's an snapshot of it on 2019-06-25: https://web.archive.org/web/20190625172349/https://vlang.io/.... Here's the page now, marked as WIP: https://vlang.io/docs#memory.
You could argue that you simply forgot to mark these. I'm not going to go into discussion about that, but I just want to say that the author's claims seem legitimate at the time of posting.
> ... and that the first public alpha release is not stable.
Another quote from the article:
> Thanks for reading this far. I hope this feedback can help make V a productive tool for programming. It’s a shame it seems to have been hyped so much for comparatively so little as a result. The developer has been hyping and selling this language like it’s the new sliced bread. It is not. This is a very alpha product. I bet you could use it for productive development as is if you really stuck your head into it, but as it stands I recommend against using it for anything.
> The language can be bootstrapped with "cc v.c" without any dependencies? Who cares!
One of the article's criticisms is that that claim isn't (wasn't?) true.