Comment by TwentyPosts
1 year ago
To be fair, I ran into a compiler bug in Zig within a few hours of using it. I'd still expect Zig to be a lot less buggy than V, based on what I heard.
Last time I looked at V it just seemed like the language wanted to have it all. No tradeoffs, just "The best parts of Rust and Go" with no explanation how that's remotely achievable (and it wasn't, judging by the attempts to make "auto free" memory management happen, and having to discover first hand that this is not a good approach, and the problem is turing complete).
Then again, out of the C alternative languages Zig, Odin and C3 - Zig’s always been the one with the most open bugs despite (or due to?) having by far the most amount of people working on it.
Ironic now when the compiler is written in Zig considering how Zig is advertising itself as being better at stability and reliability than C/C++ (the C3 compiler is written in C and Odin’s compiler is a C-like C++)
Please don't do programming language flamewar on HN. It's not what this site is for, and destroys what it is for.
If you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.
zig - 1,228 open bugs
rust - 3,670 open bugs
gcc - 17,630 open bugs
These stats don't measure what you imply they measure.
And I think you made this comment despite already knowing that.
Would you please edit out swipes from your HN comments, as the site guidelines request? https://news.ycombinator.com/newsguidelines.html
Your post would be fine without the last sentence.
https://github.com/vlang/v/issues
873 open, 7275 closed.
The ratio is important. What is it for the ones you listed?
Zig, similar to Rust, is like crawling into a syntax dumpster fire. Ugh. Give me C any day if I didn't have a choice for better options.
Please don't post flamewar comments to HN. It's not what this site is for, and destroys what it is for.
https://news.ycombinator.com/newsguidelines.html
2 replies →