This doesn't bode well for the end of Moore's law. That is Moore's law in the performance sense, i.e. guaranteed future single-core performance increases [even if small], not Moore's law as in the the doubling transistor density.
Most B2B SaaS's, which I would bet is the most common front end developer on HN, do not see significant benefits from fast loading. They will see issues with slow loading, and they can't ignore bundle size, but the benefits to development speed from a pure JS front-end from this kinds of sites is realised as value by the client.
B2C SaaS, and you start to see a different story, largely due to the wider variety of devices and more mobile friendly focus.
Non SaaS, product sales or news focused businesses facing joe public are likely as you say.
SourceHut does this. It's not a categorical impossibility, but I agree devs are generally going to be inclined to continue with 'business as usual'.
Does it really make dev work that much harder though? I'm not really qualified to comment. Presumably it's going to simplify things in at least some ways.
> do your company a favor - educate those in charge about how much page load time matters.
There you have it - the people making the case for less JavaScript may be the devs themselves.
Isn't Google's AMP just a bunch of Javascript too? So even their "fix" is just perpetuating the issue
However, ::knock on wood::, I don't seem to have encountered it that much.
Maybe it's because of how I browse, and that I don't follow "football" news, but I almost never see the URL in my browser, nor links to it anywhere.
How do people typically come across AMP content?
I use Firefox on my mobile and I always wondered why people keep complaining about Amp, since I never see it.
Moore’s law is only about the latter, it says nothing about performance.