Live data from Hacker News

Did iOS 15 kill Google AMP

lapcatsoftware.com

71–80 of 85 posts

Re: Did iOS 15 kill Google AMP

#71
post #66
post #62

Earlier quoted context omitted.

Except AMP still loads in Safari 15 if you spoof the User Agent, per TFA.

"regression" doesn't have to mean "totally broken". maybe it's a little laggy. Maybe it breaks in certain edge cases.

I don't know that I would classify "rendering someone else's feature" a responsibility of iOS 15 or Safari.

Re: Did iOS 15 kill Google AMP

#72
post #68

Side note: Does anyone have a decent link that explains exactly what AMP is to someone non technical? (Bonus if it explains why its bad, but I think I was able to at least get that part across) I have been trying to explain multiple times but I am continuing to realize that there is certain terms that I just "know" and don't really know how to translate.

Techcrunch usually has this type of articles: https://techcrunch.com/2018/02/13/amp-for-email-is-a-terribl... Since this is site is usually read by C-levels and some VC's, the language is less technical but somewhat editorialized. Anyway AMP is bad because it proposes an Internet without the freedom to push dynamic content (JavaScript, webassembly, etc...), cached at "google servers" for fast delivery but with featur…

TBH this is how I summarized AMP being bad, but some are curious more exactly what it is:

"Google tried to push something that gives Google more control, Google used the control Google already had to strongarm websites to start using it or their search results would go farther down. "

Thank you for the link, will check it out and forward it.

Re: Did iOS 15 kill Google AMP

#73

Seems unlikely. How many people have installed AMP blockers specifically on ios15? How many people have installed AMP blockers on any other platform that's not being UA-sniffed?

How many normal users have even heard of AMP? Even among those technical enough to know or care about AMP, how many have installed and use these plugins? I haven’t.

I don’t see how blockers installed by a small percentage of techies would have much impact.

Re: Did iOS 15 kill Google AMP

#74
post #56

TIL there are AMP blockers on Safari...brb

I did the same thing, that is the quickest few bucks I have spent on the App Store ever (and then shared to all of my friends). Did not even need to think about it, I have wanted this since APM first started being rolled out.

yeah, I didn’t even think twice about dropping $4 on it

Re: Did iOS 15 kill Google AMP

#75
post #60

My suspicion, having worked at google for a while, is that this is a parser / version eligibility bug. Someone probably put the list of major versions where this is supported, and 15 was not there :) Things like this happened every new ios release. Going from 9->10 was a problem for example because regex used was limiting major version to single digit etc.

There could also be a newly discovered bug or change in Safari 15 that affects AMP pages.

Re: Did iOS 15 kill Google AMP

#76
post #68

Side note: Does anyone have a decent link that explains exactly what AMP is to someone non technical? (Bonus if it explains why its bad, but I think I was able to at least get that part across) I have been trying to explain multiple times but I am continuing to realize that there is certain terms that I just "know" and don't really know how to translate.

Techcrunch usually has this type of articles: https://techcrunch.com/2018/02/13/amp-for-email-is-a-terribl... Since this is site is usually read by C-levels and some VC's, the language is less technical but somewhat editorialized. Anyway AMP is bad because it proposes an Internet without the freedom to push dynamic content (JavaScript, webassembly, etc...), cached at "google servers" for fast delivery but with featur…

This is not a good explanation. AMP4Email is different from AMP and serves a different purpose. https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245... is an explanation of what AMP does.

Re: Did iOS 15 kill Google AMP

#78

Earlier quoted context omitted.

Techcrunch usually has this type of articles: https://techcrunch.com/2018/02/13/amp-for-email-is-a-terribl... Since this is site is usually read by C-levels and some VC's, the language is less technical but somewhat editorialized. Anyway AMP is bad because it proposes an Internet without the freedom to push dynamic content (JavaScript, webassembly, etc...), cached at "google servers" for fast delivery but with featur…

This is not a good explanation. AMP4Email is different from AMP and serves a different purpose. https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245... is an explanation of what AMP does.

That is exactly the type of example/article/blog OP didn't wanted, too technical, TC article is about AMP for email but first its describes what AMP is and does, why is bad and why google is pushing AMP for literally everything it can. It's less technical more down to in tone for less technical savvy readers.

Re: Did iOS 15 kill Google AMP

#79
post #28

TIL there are AMP blockers on Safari...brb

I moved to duckduckgo because of how AMP breaks moat sites on iOS .. I too would like one of those AMP blockers

I don't use google search but every once in a while I get sent or stumble upon an amp link - so even for those limited times a $4 extension is a no-brainer.

Re: Did iOS 15 kill Google AMP

#80
post #55

I'm an AMP noob but why would someone block AMP pages?

Because the AMP pages are often functionally crippled compared to the real site and require clicks to get off and on to the real web page (see Reddit, The Guardian etc), as well as the negatives of giving Google that level of control.
Post reply on HN