Re:Standardizing lessons learned from AMP
by michaelmior on Thursday March 08, 2018 @12:44PM
(#16546059)
I don't believe it's intended to really replace AMP. It sounds like Google is establishing a set of performance guidelines (as many have been encouraging them to do). If you want to meet those guidelines, one way is to use AMP which I expect they'll continue to maintain and build on. If you don't like AMP for whatever reason, you can use whatever solution you want to meet the same guidelines.
[ Parent
| on HN ]
Re:Standardizing lessons learned from AMP
by dmitriid on Thursday March 08, 2018 @01:27PM
(#16546412)
Google has had performance guidelines for seveal years now: https://developers.google.com/speed/
Funnily enough, Google’s own AMP fails those guidelines when not preloaded and pre-rendered from Google’s own CDN: https://ferdychristant.com/amp-the-missing-controversy-3b424...
Google will continue doing what it does: caching and preloading whatever content it prefers (select publishers, select advertisers) and penalize everyone else even if they follow all of Google’s guidelines to a T.
Web Packages, no matter how well you disguise them as a web standard, will not solve that.