There's an entire article half of which is about a single checker bug that has already been fixed.
Or claims like "it uses official system api (libc), therefore you can't say it doesn't have dependencies".
1,578 karma · joined November 15, 2016
There's an entire article half of which is about a single checker bug that has already been fixed.
Or claims like "it uses official system api (libc), therefore you can't say it doesn't have dependencies".
How is that remotely irrelevant?
What kind of behavior do you expect?
(By the way there's not a single question there.)
People will keep linking to them and say "didn't you see? V uses shell to do http requests! what a joke"
This most recent article by an anonymous author had all of the issues fixed within several days, but it wasn't updated, it'll stay like this forever, as planned.
It'd take 10 minutes to submit github issues, instead they spent a month on this.
Null is only allowed in unsafe code.
Overwriting of len was never fixed, because it was never an issue in the first place. The author made it up. It's always worked like in Go.
Included libraries, you mean the json library that's part of vlib. So each Go program that uses net.http also has library dependencies by this logic.
What's wrong with the division by zero issue? It works just like in Go?
What about the openssl issue? The user didn't install the library on Windows, as was documented.
By the way, we're going to embed openssl to avoid this problem.
That's exactly what it is :)
We also have thousands of tests.
Do you have any examples?
There's actual valid criticism and feedback like in https://github.com/vlang/v/discussions/7610
But there's also trolling, harassment, and completely baseless attacks.
He enjoys language development and submits his feedback and ideas, discusses other ideas etc.
I do not work as a big censor and read every single of the thousands of messages, and I do not have time to do it.
That's not how the world works. And it's open source, where hundreds of contributors help you find and fix these bugs. That's the whole point.
Autofree hasn't been a priority because of how unexpectedly well the GC is performing with V, but it will be finished.
All this is clearly stated on the website.
2. For stuff like i++ expressions, V allows them. Some stuff gets translated to adapted V code. Some (~2% of the syntax) will result in an error. Those will be fixed this year.
3. Memory safe, bounds checking, C ABI.
4. Ridiculously easy. The main reason it was created (was using Go before). Just run `C.foo(1,2,3)`. Use C2V to generate V wrappers.
5. Only system threads for now.
6. Same as with C. Need export "C".
7. Very stable, at least for me. Never had a crash/segfault.
8. Hard to pick. Fast compilation, hot code reloading, nice clean sum types, clean json serialization and ORM (mysql,sqlite,postgres).
Also there's a big link on vlang.io, top menu.
This is how GitHub started to support V:
Everything else can be found in the "V is scam" articles. There will be a big article by me covering all that.
"Immature" != "not ready for production".
Regarding that immaturity comment, here's a good summary by someone else from this thread:
1. 2. 3.
If you can link one, that'd be great, and it'll be fixed. I've spent a lot of time verifying all claims are valid.
For example there was the "functions are pure by default except IO" which caused lots of criticism and memes. I simply changed the wording to a more verbose but correct phrase. So we do admit shortcomings and not make up excuses "for each of them"
We do not delete criticisms, we actually welcome them and any kind of feedback:
https://www.youtube.com/watch?v=gmB8ea8uLsM
0 GC is used.
None of the people who ever donated or are still donating felt they were being scammed. They often write about this here on HN.