5 ms·

AMP is just broken HTML, hardly a standard. https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.theverge.com%2Fplatform%2Famp%2F2015%2F10%2F7%2F9467149%2Fgoogle-

• flipp3r 11y ago
  I think this tweet from the AML project lead sums up pretty well how much they thought about standards https://twitter.com/cramforce/status/651769139204259840 https://twitter.com/cramforce/status/651769139204259840
  • spacecowboy_lon 11y ago
    So its Google they cant even implement the sitemaps.org standard fully to spec or handle robots.txt files with BOM markers. I wonder what the average Googler would make of OSI standards like x.400 and x.500.
• oneeyedpigeon 11y ago
  I don't understand why they don't just use data-* attributes and stay valid.
  • ducuboy 11y ago
    Absolute control.
    • magicalist 11y ago
      Please explain because that makes absolutely no sense. It's just an attribute.
• ducuboy 11y ago
  What about RSS? That offered good performance, was widely adopted and was a real standard working for both publishers and consumers. Remember who actually killed it? Yeah, that was also Google.. by discontinuing their Reader - a very good tool with lots of users but no revenue. That's how much open standards matter. Too bad @aaronsw is not around anymore, he would have said something about AMP.
  • oneeyedpigeon 11y ago
    I was as annoyed as the next person when Google killed Reader but, to be honest, RSS was killed off for typical users way before that when browser manufacturers dropped/hid support for it. I still use RSS every day, as do many of our customers.
    • ducuboy 11y ago
      Indeed, also Google Chrome.
      • magicalist 11y ago
        Chrome never had support. RSS support was always (and still is) from extensions.
    • eloisant 11y ago
      Not just browsers, but Facebook and Twitter both killed their RSS feed at some point. That's much worse than Google killing Reader, because reader is just a reader, you can still switch to a different one. If the source doesn't provide an RSS feed, there's not much you can do.
    • eloisant 11y ago
      Not just browsers, but Facebook and Twitter both killed their RSS feed at some point. That's much worse than Google killing Reader, because reader is just a reader, you can still switch to a different one. If the source doesn't provide an RSS feed, there's not much you can do.
  • coldtea 11y ago
    >Remember who actually killed it? Yeah, that was also Google.. by discontinuing their Reader - a very good tool with lots of users but no revenue. If a single company killing a sigle product could kill RSS, then it wasn't that alive in the first place. The fact is, after 10 years of RSS being available in blogs, news sites and elsewhere, Reader still had an insignificant number of users in the web scale of things. A few tens of millions (all estimates put it in the low tens, like 20 to 40 millions).
• mattlutze 11y ago
  I wonder what sort of input Vox, as a publishing partner, has had on the development of AMP. Loading the article in your validator reference shows me 80 some requests returning from 48(!) unique sources.
• kennydude 11y ago
  Interesting how on the HN link it says: > The page you are currently reading is an AMP HTML document. Yet it has a proper doctype of "<!doctype html>"
• nevir 11y ago
  Custom elements are not "broken" HTML. They're very close to being a finalized standard, too: http://w3c.github.io/webcomponents/spec/custom/ http://w3c.github.io/webcomponents/spec/custom/