It's get annoyed by JSON day! Services, if you serialize numbers >2^53-1 to JSON number literals, then make sure you tell your JS users that they can't use JSON.parse without suffering transparent data loss. Tools, if you allow comments in JSON, then it's not JSON.
-
-
Replying to @bterlson
> Tools, if you allow comments in JSON, then it's not JSON. Do you think tools should use a different extension too?
2 replies 0 retweets 0 likes -
Replying to @sebmck
I do think that. Do you say "too" because you agree or because I have other pedantic demands as well?
1 reply 0 retweets 3 likes -
Replying to @bterlson
“Too” because I’ve been thinking about this also, and have written my own JSON with comments parser
1 reply 0 retweets 2 likes -
Replying to @sebmck
In reality it's a complex question, but it would be nice to have a new extension.
3 replies 0 retweets 2 likes
New extension definitely makes sense. I think it mirrors .mjs about an expectation for parsing based on extension. I wish the JSX/Flow community had stuck with .jsx instead of overloading .js, although I guess that's partially my fault.
-
-
Thoughts on JSON5?
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 