Cool, let me know when you have a rational counterargument then, some of us have gotten fed up with Rust (especially at scale) and are very much enjoying Zig (which has no magic, which turns out to be a huge advantage at scale)
"No borrow checker" id not a reason to switch to Zig, unless you have a reason that borrow checker is limiting you from developing, hence the "I don't like this attitude". Just give the reason, not the "solution"
Not to mention we're nitpicking over something that an LLM wrote.
I'm working on 3 apps (Zig core, C FFI, Windows/Mac frontends) that haven't been released yet.
One verifies the binary data of over 200+ common filetypes, to the extent possible.
Another protects data archives/data collections with some parity, in order to survive a degree of bitrot, for those files that you don't necessarily have on a NAS.
The third is a new kind of archiver that specializes in compressing files that are already internally compressed as part of their spec.
Trivia: Did you know that the now-most-common image format in the world, Apple's HEIC/HEIF, has absolutely NO internal integrity protection, and that you can't depend on a failed decode to detect errors since all binary values are allowed in the stream format?
Cool, let me know when you have a rational counterargument then, some of us have gotten fed up with Rust (especially at scale) and are very much enjoying Zig (which has no magic, which turns out to be a huge advantage at scale)
reply