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."
This is an article by a guy who calls himself a "V hater" and the stuff from discord sreenshots wasn't even addressed to him.
What are the lies? Please list them here, I'm genuinely interested. Bugs in experimental coroutines, a new WIP feature no even mentioned on the home page yet?
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)
You are right, these are two very different tasks. That's what makes solving this fun and challenging. I had it in mind when I was designing the architecture of gitly. In the end it really is going to be easily deployed and scalable.
The default font is not proportional, BUT you will be able to set it to whatever you like. There will also be an option to disable syntax highlighting.
for example:
> Another lie, Alex himself wrote to me in Telegram, not the moderator.
the entire thing isn't even about him, but a different person, and that person was contacted by the moderator. Yet this guy thinks it's about him.
Not a very unbiased source.
Bugs and leaks don't make the project a scam. Every project has bugs.