Live data from Hacker News

Ignore the haters, and other lessons learned from creating JSON5

aseemk.substack.com

1–10 of 211 posts

Re: Ignore the haters, and other lessons learned from creating JSON5

#4

The kind of people who leave criticism on HN are not worth listening to anyway. Most of the users of this site have no taste and think they're more brilliant / important than they actually are.

Your comment is so self aware, it's almost an AI. :D

Re: Ignore the haters, and other lessons learned from creating JSON5

#6
Does ‘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.

Re: Ignore the haters, and other lessons learned from creating JSON5

#7

The kind of people who leave criticism on HN are not worth listening to anyway. Most of the users of this site have no taste and think they're more brilliant / important than they actually are.

As someone on HN, I can't say with confidence that I resemble that remark.

Re: Ignore the haters, and other lessons learned from creating JSON5

#9

Does ‘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.

If you had OpenAPI to document the JSON, where would you use comments in the JSON payload?

Re: Ignore the haters, and other lessons learned from creating JSON5

#10

Does ‘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 :/
Post reply on HN