TIL
json5.org
I can't help wonder how each new format capability impacts parsing performance though.
Of course, I don't have enough time to analyze something so silly but I really don't need both quoted and unquoted keys supported nor trailing decimals.
Conversation
It also doesn't fix the "numbers" type...
1
3
I just want a better format with proper types, comments, trailing commas, etc that can eventually be web native and shipped in all browsers. Can we just get that?
2
1
8
Wondering whether Nickel is any good: twitter.com/tweagio/status - not sure about the hopes of browser standardisation though. 🤔
1
Oh wait, by ‘types’ do you mean ‘data types’?
1
Mostly I meant that the primitive types were more sensible (e.g. differentiate between integer, natural, decimal,...) to be the minimum for my needs.
1
1
Replying to
Yeah that makes sense. I think my brain when ‘types’ and thought ‘static type checking’ not ‘datatypes’/‘primitive types’. Thinking about type systems too much heh 😅