If this was a concern it’s an admission that JavaScript developers have optimized to the best of their ability. Which is just sad.
If this was a concern it’s an admission that JavaScript developers have optimized to the best of their ability. Which is just sad.
When I first saw the CORS headers on large sites that are sent with every effin request, I thought I gone mad, only to learn that it's encouraged to be used... I remember times with monsteriusly sized cookies, this is the same, except this won't go away with the rise of server side sessions.
For technical people it's a matter of self selection. It's worse for the ones of us that can't bother checking which scripts break the page and deciding whether to enable them. It's great for the others. Personally I can't imagine using the web without uMatrix (and uBlock Origin). For the site that really breaks no matter what, if I really need it either I open it in a Vivaldi private window (I only have uBlock in that browser) or if anything else fails, I start Chrome and close it immediately after I did what I had to do.
So much poor API design out there that most would be better off with server side rendering.
...fixing the API design.
>If this was a concern it’s an admission that JavaScript developers have optimized to the best of their ability. Which is just sad.
I mean sure, but "is this the best you can do?" requires you to know what the goals are, and I suspect the issues raised in these comments are not on hardly any of the lists. New Relic and its third-party cool-usage-graphing friends are way way higher in priority.