The End of AMP
lafoo.com
The End of AMP
1–10 of 166 posts
Re: The End of AMP
#2Better late than never.
Re: The End of AMP
#3“Avoid unnecessary JavaScript, plugins and bloat, and make your site easy-to-use.”
If only web developers would follow this advice...
Re: The End of AMP
#4Sounds like just the next calculated step.
1. Introduce $badThing with claims about page load performance.
2. tell sites they need to use $badThing to get into the “carousel”
3. Scale back the requirement of #2 just soon enough that you can argue against any claims of market manipulation via your monopoly.
4. (Continue to) Profit, because 80% of the sites that implemented it aren’t going to just rip it out now that it’s there.
Re: The End of AMP
#5Sounds like just the next calculated step. 1. Introduce $badThing with claims about page load performance. 2. tell sites they need to use $badThing to get into the “carousel” 3. Scale back the requirement of #2 just soon enough that you can argue against any claims of market manipulation via your monopoly. 4. (Continue to) Profit, because 80% of the sites that implemented it aren’t going to just rip it out now that i…
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.
Re: The End of AMP
#6Sounds like just the next calculated step. 1. Introduce $badThing with claims about page load performance. 2. tell sites they need to use $badThing to get into the “carousel” 3. Scale back the requirement of #2 just soon enough that you can argue against any claims of market manipulation via your monopoly. 4. (Continue to) Profit, because 80% of the sites that implemented it aren’t going to just rip it out now that i…
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.
Not every site has an active dev, devs are hella expensive.
Vast majority of owners will have a maintenance guy to call up if something stops working to patch it, until it gets too dysfunctional and needs a re-write.
Re: The End of AMP
#7“Avoid unnecessary JavaScript, plugins and bloat, and make your site easy-to-use.” If only web developers would follow this advice...
If there's ever free CPU cycles, you bet devs will squander it.
Re: The End of AMP
#8Make no mistake: Google could have page metrics used in search ranking years ago. The reasons they introduce these now isn't because of the kindness of hearts or because they changed their minds.
Most likely (one, or some, or any of these reasons):
- there's a potential court battle regarding AMP, and Google wants to get ahead
- publishers are leaving the platform
- there are new advertising opportunities that bring as much money to Google, or more, than AMP (or are better than potentially losing money on courts and to publishers leaving)
Re: The End of AMP
#9Another entry for the Google Graveyard.
Kind of depressing when you think of all the money and engineering hours that went into trying to make websites work with AMP that could have been spent on just making their existing code less shitty...
Re: The End of AMP
#10Another entry for the Google Graveyard. Kind of depressing when you think of all the money and engineering hours that went into trying to make websites work with AMP that could have been spent on just making their existing code less shitty...
Then again, probably most of them wouldn't have bothered anyway given what the rest of the mobile web landscape looks like.