Live data from Hacker News

The End of AMP

lafoo.com

31–40 of 166 posts

Re: The End of AMP

#31
> AMP also came with the unfortunate requirement that publishers let traffic sources such as Google cache their content and serve it from their domain, such as google.com.

I think this is backwards. Google offers to host your content on their domains, and if you want that it requires you to use certain markup, and only certain ads.

If your job is monetizing content, or if you want to raise some abstract "time spend on domain" metric, then I can understand how this can be unpopular. But if your goal is to have your content read by many people, have very fast load times, and spend a bit less on traffic, then it is beneficial.

Re: The End of AMP

#32
post #26

A phyrric victory for a Web that is basically ChromeOS. Ever heard of Web Bundles? https://web.dev/web-bundles/ https://github.com/WICG/webpackage

How is Web Bundles different from .mht, which I "think", if I remember correctly is the same as MHTML. And Safari somehow support something else.....

This is a genuine question. It is such a simple feature, zipping an HTML file with all of its resources. Why do we need that many standards for it. Is it NIH syndrome or are there technical reasons in doing so?

Re: The End of AMP

#33
post #5

Earlier quoted context omitted.

i disagree with 4. Sites need maintenance and evolution. i don't know a single dev that won't eagerly drop something as impacting as amp as soon as it's an option.

(a) that assumes the dev wants to. Plenty of developers still see Google as the all-knowing all-loving mother titty that can do no wrong. Even for those who acknowledge Google may do shitty things, but are more interested in pulling their dick or what have you, rather than doing the work to make a great $thing, AMP gives them an easy out. No interpretation required, no need to worry about timings or what a "core web…

> that assumes the dev wants to. Plenty of developers still see Google as the all-knowing all-loving mother titty that can do no wrong.

I think I've only met one dev in the last 8 years that was that misguided, although I am somewhat limited in sociability so maybe just didn't realize it.

Re: The End of AMP

#36

Earlier quoted context omitted.

(a) that assumes the dev wants to. Plenty of developers still see Google as the all-knowing all-loving mother titty that can do no wrong. Even for those who acknowledge Google may do shitty things, but are more interested in pulling their dick or what have you, rather than doing the work to make a great $thing, AMP gives them an easy out. No interpretation required, no need to worry about timings or what a "core web…

> that assumes the dev wants to. Plenty of developers still see Google as the all-knowing all-loving mother titty that can do no wrong. I think I've only met one dev in the last 8 years that was that misguided, although I am somewhat limited in sociability so maybe just didn't realize it.

I'm not saying it's all, or even a lot of developers. But they exist.

Re: The End of AMP

#37
post #20

I am so happy I have been able to avoid AMP my entire career and this ensures that I will probably will never have to bother with it in the future. This 'web inside the web' stuff is so antithetical to what the web is supposed to be, I hope Google will just pull the plug like they do with just about everything else that isn't the search engine or G-mail.

Or youtube, although that makes a lot of money so probably not anytime soon.

Or ads, 'cause why do they have search at all if not to search you ads?

Re: The End of AMP

#38

Earlier quoted context omitted.

> that assumes the dev wants to. Plenty of developers still see Google as the all-knowing all-loving mother titty that can do no wrong. I think I've only met one dev in the last 8 years that was that misguided, although I am somewhat limited in sociability so maybe just didn't realize it.

I'm not saying it's all, or even a lot of developers. But they exist.

Ok, plenty made me read it as a lot.

Re: The End of AMP

#39
Please don’t let your excitement take your focus off this part of the story:

> The good news gets even better; non-AMP pages make considerably more revenue per pageview than AMP pages. Initially, I assumed this was due to the nature of how ads load on AMP, however, recent Antitrust lawsuits have proposed that hindering ad competition was a feature and that all non-amp ad tags, such as my company, Ezoic’s, were delayed by 1 second to make them less effective. It is also alleged that Google let their own exchange win, even when someone else bid more!

Somewhere, in a parallel universe, people are going to jail and paying substantial fines for this behavior. In this universe, however, politicians don’t seem to think there is a moral hazard in the fact that those of us who work in this industry see what happened and think, “if you get big enough, it doesn’t matter if you get caught.”

Re: The End of AMP

#40
post #20

Earlier quoted context omitted.

Or youtube, although that makes a lot of money so probably not anytime soon.

Or ads, 'cause why do they have search at all if not to search you ads?

Or maps, because geo searches are a source of revenue too :)
Post reply on HN