Post

Interesting data Alex! Do you mind if I read it in a video format on YouTube?

Thanks Alex. The most interesting part of the post was the data on deployed devices and networks, and the calculation for allowable download size. IMO most important (and really only) thing is the work you are doing to even the playing field. Once the web actually can compete on mobile, it will.

React Native and similar are also important ways the “web” is competing today, until it is allowed to compete fully.

I think that's true in the breach but not in the main. If teams imagine their direction of travel is *towards* the web, off of pure native, halfway homes are helpful. But most folks would be better served using iOS webviews and real PWAs everywhere else in those cases.

The fight against bloat isn't just with devs. I've seen sites where half he downloaded JS was due to ad and tracking scripts. I can block them but regular visitors don't.

Absolutely, but teams can't even begin to think about getting 3p in line until they have operational control of their first-party perf. Remediation is a serialized activity, and saying "Y is bad too" should dissuade us from fixing X.

Of course it shouldn't be an excuse. Sometimes it's just the lowest hanging fruit. I rarely see any good criticism of why big tech firms need to send me 100s of kB of js just to know someone clicked an ad or visited. Feels like big potential improvement for perfomance and privacy.

I tend to agree with most of what you are saying. What frameworks would you use if you had to create a website or a web app tomorrow? Which ones are worth exploring? I see you mentioned Astro there. Anything else?

@qwik.dev is the only one that can properly eliminate hydration, which is largely to blame for the sluggishness and upfront bloat being dumped onto users. Astro (Islands) is like the middle ground solution, which is an improvement, but why take half measures?

Ecosystem.