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.
As a concretr example, this is a common big problem for NPM, and they have to resort to blocking IPs and/or CIDR ranges.
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.
I'll never understand why those companies can't bother to set up an internal mirror.
There aren't that many companies in the world basically.
For some companies release just means another merge to master, so they are doing tens/hundreds releases a day.
Once you do enough development that this matters, you're going to be doing caching or you'll be wasting money on waiting and bandwidth.
Consider that for developers a slow build = break time. https://xkcd.com/303/
And just running npm or pip at every turn is easier than setting up all of that, so there needs to be a push to do it. And the server of those entities seem to be able to deal with the load.
In my first job we had autoscaling cloud servers that took 30-40 minutes to be operational. I told my boss we should have pre-created an image instead of installing and compiling dependencies when we started them. But he said it would not be agile.
Yes, they do. Mostly as a result of looking for infra savings, optimising job time, improving reliability after some process fails when npm is down. It takes some longer than others. It's not necessarily devs that will do it either.
> JSON5 is in the top 500 by both dependents and PageRank
that probably confirms the project is significant but doesn't answer your question.
If you did, I guess it would be anywhere that you had a description in the OpenAPI document. But I wouldn't do that.