A modest proposal
happyassassin.net
A modest proposal
1–10 of 189 posts
Re: A modest proposal
#2Yes, please! This applies to many other lists as well, not only restricted to JSON.
Besides, imagine a world of Java, Javascript, C-like anything, where you would be DISALLOWED to have a semicolon after the last statement in a block. Crazy thought, right?
Re: A modest proposal
#3Yes, please! This applies to many other lists as well, not only restricted to JSON. Besides, imagine a world of Java, Javascript, C-like anything, where you would be DISALLOWED to have a semicolon after the last statement in a block. Crazy thought, right?
In C you couldn't follow cases and labels with just a semicolon, it was an invalid statement. That's because a statement couldn't be just a semicolon. But yes, I agree.
Re: A modest proposal
#4I really dislike JSON. It's better than XML, but not by much.
There are several fundamental problems with JSON, one of which being that you have to duplicate the field names over and over again. It's just not a very structured format. Trailing commas is the least of my concerns.
I would like to see protobuf take over at this point.
Re: A modest proposal
#5The title is a possible reference to this satirical essay about solving poverty through cannibalism: https://en.wikipedia.org/wiki/A_Modest_Proposal
Re: A modest proposal
#6Yes, please! This applies to many other lists as well, not only restricted to JSON. Besides, imagine a world of Java, Javascript, C-like anything, where you would be DISALLOWED to have a semicolon after the last statement in a block. Crazy thought, right?
Javascript: automatically inserts semicolons for you at the end of a line, but doesn't allow commas at the end of a list.
Re: A modest proposal
#7I really dislike JSON. It's better than XML, but not by much. There are several fundamental problems with JSON, one of which being that you have to duplicate the field names over and over again. It's just not a very structured format. Trailing commas is the least of my concerns. I would like to see protobuf take over at this point.
It's an unstructured format, that's the point.
You can't edit a protobufs in an editor.
Re: A modest proposal
#8I really dislike JSON. It's better than XML, but not by much. There are several fundamental problems with JSON, one of which being that you have to duplicate the field names over and over again. It's just not a very structured format. Trailing commas is the least of my concerns. I would like to see protobuf take over at this point.
What formats would you suggest that are editable with a text editor and removes all the issues you have?
Re: A modest proposal
#9Yes, please! This applies to many other lists as well, not only restricted to JSON. Besides, imagine a world of Java, Javascript, C-like anything, where you would be DISALLOWED to have a semicolon after the last statement in a block. Crazy thought, right?
Welcome to Pascal.
Re: A modest proposal
#10This isn't the only problem with JSON as a standard by a long shot[1]. Like Markdown and PHP its use has grown to the point where an extremely thoroughly reviewed reference implementation and test suite would make everybody's lives easier.