4 ms·

What security vulnerabilities, exactly?

• intelVISA 3y ago
  Many :(
• brabel 3y ago
  I've never heard Andrew say you shouldn't use Zig in production because of "security vulnerabilities", but simply because Zig is quite immature (expect bugs including segfaults in perfectly "good" code) and changing constantly, not something anyone should want in a production setting.
  • wredue 3y ago
    Honestly. In a world in which JavaScript is the number one language, I’m walking back on the idea that “instability means no good for production”. 10 years ago, I thought for sure that JavaScript devs were eventually going to get sick of breaking and deprecating changes, but they’re still going strong with picking frameworks that just don’t give a shit, switching to new breaking tool chains, etc. It seems that there are A LOT of developers willing to put up with a whole lot more than I am.
• junon 3y ago
  The one I found a while back was a DOS in UTF-8 decoding. I believe it's since been fixed but things like that given that the standard library hasn't been audited. Andrew will definitely have that happen at some point but I'd not put anything Zig into production right now, personally.