4 ms·
> I really think we should stop going "it's better cause it's written in X". I wholeheartedly disagree. I'm much more interested in this because it's written i
by smt88 4y ago
> I really think we should stop going "it's better cause it's written in X".
I wholeheartedly disagree. I'm much more interested in this because it's written in Zig and not C or C++.
It tells me a few things about the code:
- naive-implementation performance should be pretty good
- written by someone who cares about details
- less likely to have race conditions and memory bugs
- attractive for new devs who want to work on a project in a next-generation language
At this point, the only reason to use a slow or unsafe language is that it's all the author knows.
- ngrilly 4y agoWhy Zig would make race conditions less likely?
- smt88 4y agoPurely from better ergonomics[1], not a compile-time guarantee like Rust has. If your tools for concurrency are better, you're less likely to make a mistake. 1. https://kristoff.it/blog/zig-colorblind-async-await/ https://kristoff.it/blog/zig-colorblind-async-await/
- jokethrowaway 4y agoI totally buy your argument (and that's why the "X in rust" took place on HN) but zig is not any safer than most modern languages: https://www.scattered-thoughts.net/writing/how-safe-is-zig/ https://www.scattered-thoughts.net/writing/how-safe-is-zig/