There has been a lot of ink spilled about how V is not as advertised. I am not going to repeat everything here, but here are some articles you can have a look at:
The same good old 5 year old article that claims V's networking uses system("curl"), complaints that V doesn't run on every single Linux distro on release, uses debug builds with slow backend to measure performance, and complaints about V using git/make/libc and even electricity.
The 2022 article about type checker bugs that have been fixed years ago, and with false claims like the string.len one.
First sentence in the reddit comment:
> V initially made some promises that seemed completely unrealistic (automatically translating any C or C++ program to V)
The fact that these things were lies at the time should frame any reading of any current promises made by the V project. I have written the project off and am not aware of its current status, but I believe that its recent history (that article from 2022 is not 5 years old) should frame anyone's reading of current promises made by the project.
To bystanders who are interested in V: I recommend that you read the articles (especially the most recent one from 2022) and alex-m's response here, and decide for yourself which side you find the most trustworthy. I have nothing more to add and will not respond further. Goodbye.
Yes and please run the examples from the 2022 articles to verify that these type checker bugs have all been fixed.
(Not that having type checker bugs makes a language a scam in the first place.)
@mort96
It's very unfortunate that you make strong claims like "None of the features which sound interesting actually work, and there's no sign that anyone working on the language has any idea how they'll make them work."