Nobody Gets Fired for Picking JSON, but Maybe They Should? · mcyoung

JSON is extremely popular but deeply flawed. This article discusses the details of JSON’s design, how it’s used (and misused), and how seemingly helpful “human readability” features cause headaches instead. Crucially, you rarely find JSON-based tools (except dedicated tools like jq) that can safely handle arbitrary JSON documents without a schema—common corner cases can lead to data corruption! (blog also has a neato minimap view of the whole entry on the side, like VSCode)