52K of CSS should be an opportunity for optimization but you're right, we're so far gone on javascript we should really focus on the mountains before the molehills.

I'm curious how much of that JS is functional and how much is adware.

The adware is typically injected onto the page by 3rd parties so it's nothing the web devs can do anything about.

> how much of that JS is functional

Lots of sites become more functional with JS disabled.

I'm more curious how much of that js is intended to load more js that has been blocked (by the browser, adblocker, hosts file/DNS, etc).

CNN specifically isn't a site I visit much, but most news sites load a ton of third-party stuff (being on mobile makes it hard to check)

It is the web devs' responsibility to say no to bs. However, very few do, and some even welcome the bloat as a job guarantee.

This is not how the web works.

That's like asking any other software dev to "say no" to letting other programs run concurrent with their own. It's just not within scope and any attempts to have your program behave this way will be impossible to maintain.

If you're a business that wants to inject ads without anyone getting in the way, all you have to do is host the pages somewhere the dev can't touch. This would likely be a CDN or similar for a multitude of other good reasons. So the content security policy is now only configurable by the admin who really doesn't give a shit and doesn't even know what's being hosted on there.

Use lite.cnn.com instead.

Tailwind v4 tree shakes too so even thats not technically bloated anymore

Tree shaking and bloat are different concerns. And, technically, is tailwind tree shaking? I thought they only built styles that the compiler could find being used rather than removing styles the compiler couldn't find being used.

Tailwind v4 tree shakes automatically on imports is what I understand.

I don't think it's identical to package tree shaking but the outcome is the same.

I don't think it was doing it before v4, or if it was, not as efficiently

Tree shaking is actually a sign of bloat. It is a tool on top of a bloated mess, to fix that mess. It would be better not to make a mess in the first place.

Type/JavaScript are extremely tree shakable if using esm.. what makes you think it's not?

Only at the most crude level. Ever heard of "virtual functions"?

Runtime polymorphism is great but I wouldn't consider that to be tree shaking.