Weird JSON
Data
serialization format
SHOW HN2020
67points
39comments
#895of 3,028 in 2020
Top 30%of 2020 by points
How HN took it
MixedNo clear lean
5 positive, 5 neutral or asking, 2 mixed, 3 critical, out of 15 comments about the project. Thread score +0.21.
Idea: 3 for, 2 againstPerformance: 1 for, 0 againstExecution: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful for legacy systems that need richer types than JSON
From 1 comment
Sorry, but this is awesome. It's not really what you probably want in most situations. But sometimes you have constraints that come with legacy systems. Adding another layer of…
montroser on HN
Fun and well made
From 2 comments
Amazing job! JSON can be improved like HTML 1.0
ellis0n on HNHaters gonna hate, go for it!
francisduvivier on HN
Objections
Seen as a security risk and not for production use
From 2 comments
This sucks. Real JSON is waay better than OP. Or at least use Protobuf, it's popular and created by Google, or bson. Don't use this, it's clearly a security nightmare.
jauco on HNI mean it's clearly a joke, but... Why not? A new standard, great idea! Just a reminder to everyone, try this out in production!
w-m on HN
Adding types to a data format creates interoperability problems
From 2 comments
I'm of the opinion that any types other than strings in JSON is a mistake - any parsing assumptions will _never_ be future sufficient. It should be the user of the library's…
bArray on HNTo me the "NULL" of JSON is really the lack of a value. I think having a NULL value could introduce problems. For example: Did you set `{"address":null}` or did you set…
bArray on HN
Requests
Specify a datetime type
From 2 comments
And still no specification for `datetime`. I can't for the life of me understand why protocol specs omit this.
dmitriid on HNNah. The notion of a "time since arbitrary epoch" is pretty universal, even though it may have a variety of representations. Just pick one, it really doesn't matter which.…
stickfigure on HN
Support comments in files
From 1 comment
If you're going to enhance JSON, you might consider how you could support comments in unencoded files at-rest on disk.
bonkabonka on HN
Questions
Why is it named 46 and why is it called JSON
From 1 comment
Hmm, interesting idea. Have you ever heard of Base64? Just curious why you chose to name it 46? And why JSON? There's specific definitions of 46, and JSON, and they don't say…
yamrzou on HN
Alternatives named
Cap'n Proto
From 1 comment
Sorry, but this is awesome. It's not really what you probably want in most situations. But sometimes you have constraints that come with legacy systems. Adding another layer of…
montroser on HN
Protobuf and BSON
From 1 comment
This sucks. Real JSON is waay better than OP. Or at least use Protobuf, it's popular and created by Google, or bson. Don't use this, it's clearly a security nightmare.
jauco on HN
JSON5
From 1 comment
Like JSON5?
taywrobel on HN