Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I totally agree than in 2006 it made sense for JSON to focus on the minimal agreeable subset of syntax needed to describe what it describes. But it's coming up on 20 years old. If in 2010, JSON had a 1.1 version that was basically json5, we all could be using it now with full interoperability. That is how formats evolve.
JSONs make terrible config files. If you want to use json-like syntax for config, use hjson instead. It's basically json, but changes it slightly so it better matches human expectations.
Well, there is JSONC for those who do want those comments
To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.