Whenever I need to use JSON in my projects I always check if I can use JSON5 instead. It really makes a difference to have a more user friendly format. My only gripe is when I use Python, the official JSON5 module is much, much slower than Python's JSON parser. I frequently end up translating the development JSON5 files to JSON files that go into the final runtime because of this.
Ignore the haters, and other lessons learned from creating JSON5
11–20 of 211 posts
Re: Ignore the haters, and other lessons learned from creating JSON5
#12Does ‘downloads per day’ actually mean anything? It could be someone large company’s CI system building on every commit. I don’t think I’ve ever seen a JSON5 file in the wild. I’ve always wanted comments in JSON, but the other issues highlighted are not things I care about. The ‘be lenient in what you accept’ philosophy is a disaster, just look at HTTP… stricter is better IMO.
Although I cannot assume, I'd at least hope that a "large company’s CI system" would cache the frequently encountered version(s) of a certain dependency :/
Not a safe assumption. They tend to only invest effort into caching after getting blocked.
As a concretr example, this is a common big problem for NPM, and they have to resort to blocking IPs and/or CIDR ranges.
Re: Ignore the haters, and other lessons learned from creating JSON5
#13Does ‘downloads per day’ actually mean anything? It could be someone large company’s CI system building on every commit. I don’t think I’ve ever seen a JSON5 file in the wild. I’ve always wanted comments in JSON, but the other issues highlighted are not things I care about. The ‘be lenient in what you accept’ philosophy is a disaster, just look at HTTP… stricter is better IMO.
Does ‘downloads per day’ actually mean anything? It could be someone large company’s CI system building on every commit.
I don't think you understand quite how many 60,000,000 downloads per week is if you think a big company's CI pipeline might account for that.
Re: Ignore the haters, and other lessons learned from creating JSON5
#14I don't think writing an article about hackernews comments from two years ago is exactly what I'd call a lesson in ignoring the haters, but this reads a little bit like someone writing an article about the roaring success of null references after their adoption.
despite popularity, most of the technical comments in that original thread aren't wrong. 'Popular', 'Easy to adopt' and 'a very bad idea' can be overlapping circles, in particular in the world of javascript and npm
Re: Ignore the haters, and other lessons learned from creating JSON5
#15I enjoy using json5. I solves a real problem imo..
Regarding the criticism, I get the same bad energy when people get a kick out of fixing someone’s grammar, and then do not even comprehend what is being complicated.
Well done on the lib and thanks for building something useful! Good writeup also! Think I’m going to give the commit access trick a shot.
Re: Ignore the haters, and other lessons learned from creating JSON5
#16Honestly I don't understand why JSON should be human-readable. It is a data serialization format intended to be read by software.
Just adding comments and multi-line strings doesn't make it human-readable, it is still too bloated and I don't like writing it manually. If you want a human-readable format, try at least to remove unnecessary quotes, brackets and commas and make it look similar to YAML.
JSON is not intended to be used in configs and other user-editable files.
Re: Ignore the haters, and other lessons learned from creating JSON5
#17The only 2 things I'd like to add in JSON are trailing commas and comments, and this is already supported in most JSON configs (.eslintrc, .babelrc, ..), it's called JSONC I believe
Re: Ignore the haters, and other lessons learned from creating JSON5
#18I don't think writing an article about hackernews comments from two years ago is exactly what I'd call a lesson in ignoring the haters, but this reads a little bit like someone writing an article about the roaring success of null references after their adoption. despite popularity, most of the technical comments in that original thread aren't wrong. 'Popular', 'Easy to adopt' and 'a very bad idea' can be overlapping…
Ten years?
Re: Ignore the haters, and other lessons learned from creating JSON5
#19I'm kind of appalled that the Hashicorp guy went that far to put someone down for just building something they found useful to themselves. What a great way to discourage someone from expressing themselves creatively. Glad Aseem carried on regardless.
No post body was provided.
Re: Ignore the haters, and other lessons learned from creating JSON5
#20Honestly I don't understand why JSON should be human-readable. It is a data serialization format intended to be read by software. Just adding comments and multi-line strings doesn't make it human-readable, it is still too bloated and I don't like writing it manually. If you want a human-readable format, try at least to remove unnecessary quotes, brackets and commas and make it look similar to YAML. JSON is not intend…
Because it's really handy to be able to run things like rest requests without any tooling more than curl or postman?