Chronotope’s avatarChronotope’s Twitter Archive—№ 147,111

  1. …in reply to @librenews
    MTerenzio jeffjarvis Also because--in my entire career--I never met more than mby half a dozen web developers, in the publishing industry or outside of it, who liked developing with it or dealing with its often very entirely arbitrary restrictions.
    1. …in reply to @Chronotope
      MTerenzio jeffjarvis Look... whatever AMP *wanted* to do. I think it's pretty fair to say that looking back at it we don't see it accomplishing that very effectively. Outside of the Google cache it often even failed to actually deliver better speed. Part of the problem was def Google's top down push.
      1. …in reply to @Chronotope
        MTerenzio jeffjarvis And while AMP is a tool for distribution... the reality is that the design of the specification made that adoption fundamentally difficult enough that few other companies picked it up for that use. It's a lesson in Google's hubris & failure to get larger participation pre-launch.


Search tweets' text