5 ms·

AMP Adds Support for Server-Side Rendering

• andrerm 7y ago
  Why is Google pushing this crap so hard? It can't be just because of "speed". Can it?
  • PedroBatista 7y ago
    Control. Control gives you all the options to make the future you want.
• ocdtrekkie 7y ago
  The beautiful irony is in how many seconds it took this blog post to load. At least five or six seconds.
  • ce4 7y ago
    It took 8 seconds on my Firefox mobile... also on the second reload.
    • rogual 7y ago
      Google's AMP code creates an intentional 8-second delay if you're blocking their tracking scripts. Could be that.
      • ce4 7y ago
        Lol, thanks - didnt know that. Then that's very probably the case here as I'm of course blocking their stuff.
• pictur 7y ago
  But why?
  • Khaine 7y ago
    embrace extend extinguish Google is using the old Microsoft strategy
• jaredcwhite 7y ago
  No thanks.
• ricardobeat 7y ago
  Sad to see Next.js supporting AMP.
• barbarbar 7y ago
  Now there is Angular 1, Angular 2+, material design lite,material design not-lite, Polymer1+2, Polymer3, lit-html, Flutter and AMP. What is the main purpose for google producing all these often competing and proprietary frameworks?