Developer argues JSON.stringify is fundamentally broken and should be replaced

A software developer and open-source contributor named Dmitry has published a detailed technical argument urging JavaScript developers to stop using JSON.stringify entirely. He documents multiple silent failure modes in the built-in method, including undefined returns for certain inputs, data loss with Map and Set objects, and incorrect null substitution for Infinity and NaN values. These issues produce no errors or warnings, making bugs difficult to trace and potentially costly in production applications. Dmitry draws a parallel to the 2019 'Parse, don't validate' movement, proposing a new principle he calls 'Encode, don't stringify' as a replacement philosophy. He advocates for schema-based encoding libraries, including his own project Sury, as safer alternatives that handle serialization explicitly and predictably.