Sweet, it supports trailing commas! Single biggest personal JSON annoyance.
Personally, I really hope Human JSON, https://github.com/tailscale/hujson , will get more popular!
https://www.freecodecamp.org/news/comments-in-json/
They were removed from the standard because some were using them for custom parser directives.
Who wants to type `{name: "pveierland"}` when you could just do `{name "pveierland"}`?!
`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.
Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.
Personally, I much prefer the latter of these two:
JSON:
[
{
"id":"0003",
"type":"donut",
"name":"Old Fashioned",
"ppu":0.55,
"batters":{
"batter":[
{
"id":"1001",
"type":"Regular"
}
]
},
"topping":[
{
"id":"5004",
"type":"Maple"
}
]
}
]
[{"id" "0003"
"type" "donut"
"name" "Old Fashioned"
"ppu" 0.55
"batters" {"batter" [{"id" "1001"
"type" "Regular"}]}
"topping" [{"id" "5004"
"type" "Maple"}]}]
EDN
[{ "0003"
"type" "donut"
"name" "Old Fashioned"
"ppu" 0.55
"batters" {"batter" [{"id" "1001"
"type" "Regular"}]}
"topping"
}]
{:id 3, :type, :ppu 0.55, :topping}
{
:id 3,
:type :ppu,
0.55 :topping,
}
Check this[0] out:
[
id [0003]
type [donut]
name [Old Fashioned]
ppu [0.55]
batters [
batter [
[
id [1001]
type [Regular]
]
]
]
topping [
[
id [5004]
type [Maple]
]
]
]
For a bit more error-checking-thru-redundancy we could analyze indentation (one reason why I recommend C-style rather than Lisp-style formatting) and warn if we detect any inconsistencies.
Ergo: through design magic we can get rid of a lot of the redundancy and increase desirable properties, without trading off much of the positive side.
NB for a machine we could compact the above into:
[id[0003]type[donut]name[Old Fashioned]ppu[0.55]batters[batter[[id[1001]type[Regular]]]]topping[[id[5004]type[Maple]]]]
With your argument, JSON is equally bad because you could have {"name": "wizzwizz4", "age": 16} and ooops, some things got deleted and now the structure ends up being {"name": 16} which isn't really a sound argument against the format itself.
Another situation, due to the same defect:
{:name Jason Bourne, :age 320 000}
{"name": "Jason Bourne", "age": 320 000}