Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Sort of, except JSON is a fair bit worse since you can't have comments to explain why things are the way they are.


sort by: page size:

The only problem with json is that you can't do comments with the default implementation.

I'm fine with JSON except it doesn't officially do comments, but that's a big deal IMO

I agree. Also if json had comments, people would start putting data in comments so soon you would have to parse comments as well. Then someone would ask for ' for strings and whole json would turn into garbage.

If JSON had comments, I'd be fine with it.

Except that JSON doesn't have anything like processing directives or even comments.

Or commenting JSON?

My biggest complaint with JSON is the lack of support for comments. For that reason, it's hard to take it seriously for human-maintained configurations.

JSON is a terrible configuration format since it doesn't support comments.

If crap design like JSON is the right engineering choice sometimes (and I agree that it is), that seems like an argument that adding comments in this crappy way may sometimes be the right engineering choice.

I love json but despise the fact it doesn't support comments

JSON is great, but I surely wish it supported comments. That's the nature of its failings: too minimal.

So you're saying JSON doesn't support comments

JSON is an example of 'worse is better'.

Json is completely fine. It's just too bad it doesn't have any support for comments. Maybe a future revision could add it?

I think JSON would be vastly improved if it were to just allow comments. Maintaining configuration in JSON is unnecessarily painful due to this pointless feature gap.

Hum... JSON is quite easy to write. Too bad the lack of comments makes it unmaintainable.

As the OP said, the quest for the perfect data language is still on.


You can, but you lose the possibility of comments, and writing JSON by hand is also a pain in the ass...

Sure doesn't look like it..

I agree- that's why json is honestly great. I avoided it for the longest time, but now I totally see the appeal.


The point is that all those problems are strictly worse with plain JSON.
next

Legal | privacy