3 ms·
Opposite of web standards? It's HTTP+HTML+JS+CSS. What part of AMP isn't standards compliant?
by madeofpalk 9y ago
Opposite of web standards? It's HTTP+HTML+JS+CSS. What part of AMP isn't standards compliant?
- slackingoff2017 9y agoThe AMP client source is available but worthless. Google validates that you're running their blessed version of the framework and if you change a single bit in the files Google doesn't serve your AMP content anymore. It's a classic walled garden, like the Android app store. You can develop Android apps that don't meet their guidelines but you can't distribute them through normal channels.
- Larrikin 9y agoThe Play Store is pretty liberal in what they allow, more so than the Apple App store atleast.
- madeofpalk 9y agoRight, so its closed source? Still standards compliant.
- grey-area 9y agoWhat part of AMP isn't standards compliant? The part that mandates including js from a corporation on your pages.
- madeofpalk 9y agoYes, using a javascript framework requires you to have that javascript on your page.
- matt4077 9y agoOP is complaining about Safari not supporting the most recent APIs, whereas AMP supports only an extremely limited subset of all those technologies. But I believe the larger issue is how it makes URL meaningless, and futures a centralisation of the web. It's not against the standard, but certainly the spirit of the web as it was supposed to be.