4 ms·
While writing a quick JSON5 parser, I encountered this old thread of incendiary takes from the HN community on the initial JSON5 proposal. Make of it what you w
by ninepoints 3y ago
While writing a quick JSON5 parser, I encountered this old thread of incendiary takes from the HN community on the initial JSON5 proposal. Make of it what you will.
- rewmie 3y agoIf anything, to me it seems all comments critical of json5 were right on the money.
- ninepoints 3y agoThe comments, to my eye, have aged extremely poorly.
- mort96 3y agoHow so? Almost all of the criticism is about how JSON5's changes make it a worse data interchange format. It's not meant to be a computer<->computer data interchange format, it's meant to be used in contexts where humans are involved, such as for config files. Would you think criticism of TOML for having comments would be "right on the money"? No? Then why do you think differently for JSON5?
- aschearer 3y agoA bunch of folks bloviating why it's a terrible idea and no one will use it. Meanwhile it's become extremely popular. And you're conclusion is they're "right on the money?" Um, OK.
- rewmie 3y ago> Meanwhile it's become extremely popular. What's your definition of "extremely popular"?
- _eojb 3y agoUsed by sqlite, babel, others, and millions of downloads not good enough for you?
- pwdisswordfishc 3y agoSo, ignored everywhere other than (reluctantly) SQLite and the dumpster fire that is NPM?
- rewmie 3y ago> Used by sqlite, babel, others (...) I believe SQLite "uses" json5 in the sense that one of its important customers asked for json5 ingestion, and json5 was supported only for input in the spirit of the robustness principle. From the horse's mouth. "The important point to keep in mind is that SQLite will read JSON5, but it never writes it. The JSON that SQLite generates is canonical JSON that is fully compliant with the original JSON spec." https://news.ycombinator.com/item?id=35962213 https://news.ycombinator.com/item?id=35962213 If your definition of success is accepting an extension because an important customer asked for an extension, so be it. In the meantime, are you sure you want to compare plain old JSON with the mess that's JSON5? Because projects such as SQLite explicitly refuse to support JSON5, and apparently their decisions pass off as the definition of success. > and millions of downloads Are you sure you want to use that as a success metric?
- mort96 3y agoShit if my spec was incorporated into juggernauts like SQLite I would certainly count that as a tremendous success, but if your standards are higher than that then I guess that's mainly just a semantic discussion.
- camgunz 3y agoThis sounds to me like SQLite fully supports JSON5, but always outputs JSON for compatibility reasons, rather than any kind of animus against JSON5.