Chronotope’s avatarChronotope’s Twitter Archive—№ 52,621

          1. …in reply to @mathewi
            mathewi "Websites can be made “AMP-compliant,” by including a piece of code from Google’s ... on their websites." fortune.com/2015/10/07/google-amp-news-mobile/
            Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
        1. …in reply to @Chronotope
          mathewi And "all resource loading is controlled by the AMP library" ampproject.org/how-it-works/
          OpenGraph image for ampproject.org/how-it-works/
          Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
      1. …in reply to @Chronotope
        mathewi Even assuming that Google isn't proposing a wholesale switch (which it looks like it is to me) there's still massive technical cost
        Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +2 🙂
    1. …in reply to @Chronotope
      mathewi Publishers would have to maintain two pages, expensive in its own right. Esp when no CMS is programed to generate AMP code.
      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -1 🙁
  1. …in reply to @Chronotope
    mathewi And restrictions of AMP would still fall down on to the standard pages. You can't even use standard CSS github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md#stylesheets
    OpenGraph image for github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md#stylesheets
    On twitter.com Twitter logo Chronotope’s avatar Mood 0

Search tweets' text