3 ms·
1. AMP is not HTML5-compatible beginning with their amp declaration. 2. AMP is a set of web components that rely on JS to properly render. 3. If JS is disable
by dmitriid 7y ago
1. AMP is not HTML5-compatible beginning with their amp declaration.
2. AMP is a set of web components that rely on JS to properly render.
3. If JS is disabled, page content is hidden by a CSS declaration
4. AMP pages are treated differently by the dominant search player
So yes. On the surface it’s “just plain HTML page”. Technically.
- acqq 7y agoAlso, on my iPhone I can never open articles on AMP in the "Reader view", destroying my accessibility needs. The articles that were completely readable in the original form become 100% unreadable as soon as they are AMP. It can still be verified on the publisher’s site that there it works, but how long will that remain? Long ago, it was seen that Microsoft had the policy "our OS isn't finished if the competior's program is still functioning." Google's “OS” is effectively all the web resources they control and then they "accidentally" miss to support Apple's browsers. Especially when they manage to bring all the news content producers to use their “technology.” AMP is evil. Behind seemingly “technical” solution is a huge additional monopolisation of the web by Google. Purely seen on that level it should be illegal. It’s in the interest of the society to allow the competition and disable the strengthening of the monopolies.
- dmitriid 7y ago> and then they "accidentally" miss to support Apple's browsers. And Firefox. See this thread by Jonathan Nightingale about Google breaking FF on purpose: https://mobile.twitter.com/johnath/status/1116871231792455686 https://mobile.twitter.com/johnath/status/111687123179245568...