3 ms·

AMP on iOS is profoundly buggy. Rotation, reader mode, and URL bar hiding are routinely broken in all modes. AMP in landscape is particularly unusable. Google

AMP on iOS is profoundly buggy. Rotation, reader mode, and URL bar hiding are routinely broken in all modes. AMP in landscape is particularly unusable. Google should be embarrassed to have shipped this.

londons_explore 7y ago
To be fair, iOS safari is becoming the IE6 of the mobile world.
- dmitriid 7y ago
  It’s not. They are just not rushing to implement half-baked standards that are being hastily designed and forced down everyone’s throat by a handful of Google engineers.
  - manigandham 7y ago
    What standards are lacking?
    - dmitriid 7y ago
      Just an example, quoting Dan Abramov [1]: "Features like service workers are touted as a solution to many problems in the web, but their ergonomics are so under-designed that people actually have to change domains to bust the cache from a broken build (I’m not making this up)." Service Workers is drafted by 4 people. 3 of them are from Google. [2] A lot of standardisation work on web standards is completely taken over by Google. A lot of discussions on JS and HTML are being handled by the same group of ten or so people who are in every open issue and every open proposal on GitHub. A common thread is "oh yes, we should involve the wider web community that's why we reached out to Angular and Polymer for comments", which are, unsurprisingly, also Google projects. A recent proposal where I saw this happen is a proposal by Apple, Template Instantiation [3] Which is now almost entirely taken over by Google. See for example this issue: [4]. Three engineers from Google decided on the future of the project and chose only Angular and Polymer as the frameworks to talk to. And you can see this everywhere. [1] https://dev.to/dan_abramov/comment/6kh1 https://dev.to/dan_abramov/comment/6kh1 [2] https://w3c.github.io/ServiceWorker/ https://w3c.github.io/ServiceWorker/ [3] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md https://github.com/w3c/webcomponents/blob/gh-pages/proposals... [4] https://github.com/w3c/webcomponents/issues/747 https://github.com/w3c/webcomponents/issues/747
    - dmitriid 7y ago
      More. Just today: https://twitter.com/Rich_Harris/status/1161642299761266689 https://twitter.com/Rich_Harris/status/1161642299761266689 Quote: “This spec (whose three editors are all Googlers) was shipped in Chromium and presented as a fait accompli despite objections.” More at the link
- iforgotpassword 7y ago
  I'm somewhat happy that's the case. And I've been an IE6 hater myself for keeping the web back. But let's face it, Firefox isn't in a position to save the web from Google ducking it sideways to their liking, so safari is pretty much the only thing with some significance, able to push back. AMP being broken there is good news to me. Hope they don't bother improving this so some users will just be driven away to other search engines.
auslander 7y ago
That's Apple standing its ground. End result is my default search is Bing, without these AMP links. I also noted that on VPN Google shows Ads in 6 out of 10 first page results.
- lern_too_spel 7y ago
  Bing has its own AMP cache.
  - auslander 7y ago
    Well, thanks. Good thing is Bing's top results are not all AMPs. Yet.

londons_explore 7y ago

To be fair, iOS safari is becoming the IE6 of the mobile world.

dmitriid 7y ago
It’s not. They are just not rushing to implement half-baked standards that are being hastily designed and forced down everyone’s throat by a handful of Google engineers.
- manigandham 7y ago
  What standards are lacking?
  - dmitriid 7y ago
    Just an example, quoting Dan Abramov [1]: "Features like service workers are touted as a solution to many problems in the web, but their ergonomics are so under-designed that people actually have to change domains to bust the cache from a broken build (I’m not making this up)." Service Workers is drafted by 4 people. 3 of them are from Google. [2] A lot of standardisation work on web standards is completely taken over by Google. A lot of discussions on JS and HTML are being handled by the same group of ten or so people who are in every open issue and every open proposal on GitHub. A common thread is "oh yes, we should involve the wider web community that's why we reached out to Angular and Polymer for comments", which are, unsurprisingly, also Google projects. A recent proposal where I saw this happen is a proposal by Apple, Template Instantiation [3] Which is now almost entirely taken over by Google. See for example this issue: [4]. Three engineers from Google decided on the future of the project and chose only Angular and Polymer as the frameworks to talk to. And you can see this everywhere. [1] https://dev.to/dan_abramov/comment/6kh1 https://dev.to/dan_abramov/comment/6kh1 [2] https://w3c.github.io/ServiceWorker/ https://w3c.github.io/ServiceWorker/ [3] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md https://github.com/w3c/webcomponents/blob/gh-pages/proposals... [4] https://github.com/w3c/webcomponents/issues/747 https://github.com/w3c/webcomponents/issues/747
  - dmitriid 7y ago
    More. Just today: https://twitter.com/Rich_Harris/status/1161642299761266689 https://twitter.com/Rich_Harris/status/1161642299761266689 Quote: “This spec (whose three editors are all Googlers) was shipped in Chromium and presented as a fait accompli despite objections.” More at the link
iforgotpassword 7y ago
I'm somewhat happy that's the case. And I've been an IE6 hater myself for keeping the web back. But let's face it, Firefox isn't in a position to save the web from Google ducking it sideways to their liking, so safari is pretty much the only thing with some significance, able to push back. AMP being broken there is good news to me. Hope they don't bother improving this so some users will just be driven away to other search engines.

auslander 7y ago

That's Apple standing its ground. End result is my default search is Bing, without these AMP links. I also noted that on VPN Google shows Ads in 6 out of 10 first page results.

lern_too_spel 7y ago
Bing has its own AMP cache.
- auslander 7y ago
  Well, thanks. Good thing is Bing's top results are not all AMPs. Yet.