How to fight back against Google AMP as a web user and a web developer

Post by EamonnMR » Fri, Dec 06, 2019, 11:48 AM UTC

account42 wrote: post #495

rdiddly wrote: post #421

Great post, although I'm a little meh on lazy-loading images. I like when the whole page is finished loading the moment I think it's finished loading. But more to the point, lazy-loading can be a crutch just like AMP is, for solving problems that shouldn't exist, such as: your page is big & bloated. If you keep it small, there's no need for lazy-loading. But you have to limit the number of images, and optimize the on…

Yeah, please don't add lazy loading. - It breaks viewing the site with javascript disabled. - It prevents viewing the site offline (e.g. on an airplane) without first scrolling through the whole content while online. - Unless implemented perfectly it adds delays before content you have scrolled to becomes visible. Deciding when to load stuff should be the browser's job. Don't reimplement the browser in javascript.

Post by squiggleblaz » Fri, Dec 06, 2019, 12:09 PM UTC

account42 wrote: post #495

rdiddly wrote: post #421

Great post, although I'm a little meh on lazy-loading images. I like when the whole page is finished loading the moment I think it's finished loading. But more to the point, lazy-loading can be a crutch just like AMP is, for solving problems that shouldn't exist, such as: your page is big & bloated. If you keep it small, there's no need for lazy-loading. But you have to limit the number of images, and optimize the on…

Yeah, please don't add lazy loading. - It breaks viewing the site with javascript disabled. - It prevents viewing the site offline (e.g. on an airplane) without first scrolling through the whole content while online. - Unless implemented perfectly it adds delays before content you have scrolled to becomes visible. Deciding when to load stuff should be the browser's job. Don't reimplement the browser in javascript.

Post by ryencoke » Fri, Dec 06, 2019, 12:38 PM UTC

squiggleblaz wrote: post #500

dunstad wrote: post #474

Earlier quoted context omitted.

There's nothing wrong with it, I've been using it for ages.

Well, once a webpage has played audio there's a notification that hangs around till you restart the phone. That's probably better than the cost of running Chrome, though.

Post by EamonnMR » Fri, Dec 06, 2019, 1:20 PM UTC

squiggleblaz wrote: post #504

EamonnMR wrote: post #501

Earlier quoted context omitted.

I'd love to see a lazy loading idiom implemented in pure HTML. But I'm not holding my breath.

What's wrong with ? Maybe some kind of semantic purpose vs but you can imagine every website owner will think that their logo is graphical content and respectful UA authors will need to disregard the semantic attributes and try to guess based on the presence or absence of some kind of caption, for instance. UAs could easily lazy load by default on metred connections.

Post by exabrial » Fri, Dec 06, 2019, 1:40 PM UTC

account42 wrote: post #499

exabrial wrote: post #236

I remember looking at the original HTML5 spec and going, there is no way lower power / low bandwidth / high latency devices will be able to handle this efficiently. Nevertheless, we moved fast and broke things, ratified the HTML5 spec and paved the cowpaths without a second thought to language or efficiency. Somewhere along the line, things came full circle. HTML was slow again, so we needed a new new way to efficien…

In what way is HTML5 is inherently slower than previous versions? Pages tend to be slow because of the tracking and adds addded to them as well as client-side "rendering" for static content. None of that is required by HTML5.