> The problem with not using JSON is that the alternative almost always is "some proprietary format" or "an undefined dialect of something that looks like a wel

> The problem with not using JSON is that the alternative almost always is "some proprietary format" or "an undefined dialect of something that looks like a well-known format". Sorry, that’s nonsense. JSON is young. We lived happily with many easy to read & parse file types before JSON arrived. Everything has changed because CPUs are fast now (so parsing overhead isn’t noticed) and storage isn’t worried about (JSON is bloated).