3 ms·

There are many json alts, but at the end of the day unless it's supported everywhere, it kinda defeats the point, because what makes JSON great is that it's sup

There are many json alts, but at the end of the day unless it's supported everywhere, it kinda defeats the point, because what makes JSON great is that it's supported almost everywhere.

hajile 6y ago
Once upon a time (a mere decade ago) JSON support was nowhere.
dmurray 6y ago
90% of when I use JSON is when I control both sides of the interaction. E.g. a web app where I have no expectation of third party clients, or a config file that will only reasonably be read by one program. JSON is normally "good enough" as a general wire interchange format, and it's human-readable and whoever comes after me will already be familiar with it. But if there's a time when it's not good enough and its failures are in expressiveness, I'd totally consider JSON5 or some other alternative instead.
- baddox 6y ago
  Even for end-to-end internal projects, as soon as you stop using a built-in format and need to use thirdPartyEncode and thirdPartyDecode on both ends, you might as well just choose the absolute best third party library rather than choose something that slightly enhances the built-in.