…e it points out how much page speed trades off against the things that make the web platform great. If the very smart engineers at Google have determined that we can’t have speed, programmability, and openness all at the same time, the mobile web platform as we know it is clearly in a troubling, and very deep, crisis.
One of the key things I note in AMP is that it is trying to get around the key challenge of HTML vs apps — pushing the UI down with every page load and filling in the details. The “render once” process is a smart way to make browsers load faster and points out that it isn’t so much as the amount of data that gets passed to the browser that is the challenge, but the non-deterministic nature of what the browser renders each time.
But I still feel there is a bit too much Google in here vs an open standard. Their immediate offering of a caching server makes it look like they want to the point of call for as many AMP pages as possible — similar to what we are seeing with Facebook Instant Articles. I’d like to see a world where Mozilla takes this over, and where Google pushes this truly as an open standard without any fringe benefits…