How to fight back against Google AMP
markosaric.com
markosaric.com
Fear not, however: https://news.ycombinator.com/item?id=23322730 is there to fill your AMP-fighting needs.
Not to mention, knowing about their ecosystem, I shudder to think of the size of some of these JS libraries performing the lazy loading.
Is that true? I believe that they kick off the requests to load images from top to bottom, but I don't think they prioritise bandwidth in such a way that downloading image #3 will never make downloading image #1 slower.
[0] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/im...
I'm not sad about any of that. I'm sad because the author skips right past a key point: how we got here. Why are websites slow, when there are good reasons to want to be fast? In my opinion, this isn't some kind of cosmic accident. It's not because most people building websites don't care or are incompetent.
Slow websites are, to my mind, a symptom. The disease is that there are economic incentives to do the things that make websites slow. Well-intentioned software engineers and web developers who like fast, light, clean websites are often not positioned to win the political battles required to cut unnecessary elements, third-party scripts, and so on.
Openness and respect for user privacy are wonderful, incredibly appealing things. I don't think I've ever been able to lean on then to convince other parts of a company to forego revenue, reach, or measurability. This could easily be an effect of my limited skills of persuasion.
I hope others have had different experiences.
Cf. Chesterton's fence.
Trying to submit https://markosaric.com/google-amp/?dummy=234 results in "Unknown or expired link"