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.
Did iOS 15 kill Google AMP
81–85 of 85 posts
Re: Did iOS 15 kill Google AMP
#82Earlier quoted context omitted.
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
#83Earlier quoted context omitted.
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.
You can't understand any of those things unless you understand what AMP does, and (despite what you claim) the TC article doesn't explain what AMP does. Not understanding what AMP does leads you to make nonsensical statements like that AMP can be replaced with a CSS stylesheet, so users continue to prefer AMP because there remains no better alternative for doing what it does.
Re: Did iOS 15 kill Google AMP
#84Earlier quoted context omitted.
You can't understand any of those things unless you understand what AMP does, and (despite what you claim) the TC article doesn't explain what AMP does. Not understanding what AMP does leads you to make nonsensical statements like that AMP can be replaced with a CSS stylesheet, so users continue to prefer AMP because there remains no better alternative for doing what it does.
You are looking at the problem from a developer perspective, not from a user/reader or content creator, your article just gives tops 1 paragraph to the issue at start talking about syntactic validation and micro-optimizations that the user/reader doesn't care. The point is we don't need AMP, we can deal with caches and the bullshit micro-optimizations ourself, ppl don't care if the page loads instantly or in 4s-6s, d…
It is not just Google (and Microsoft and the other companies that implement AMP caches) that believes users want instant loading. Apple and Facebook have products competing with AMP that give users instant loading but that are far more restrictive on the publisher and on the reader. The only reason that publishers and readers put up with that is instant loading.
Re: Did iOS 15 kill Google AMP
#85Earlier quoted context omitted.
I don't care too much about AMP links but I bought Amplosion just to show my support for Christian, the author of Apollo. That app alone makes Reddit bearable. The official Reddit app is terrible and actively harms the browsing experience and makes it harder to find actual useful content on Reddit as opposed to all the pushed spam content.
For anyone on android, "Reddit is fun" is hands down the best I've used. I seriously don't see how people put up with the main app + non old.reddit.com site. It's just miserable and ad filled.