The 10000ft perspective on AMP was correct, the lived reality was awful. And the technical implementation used can't be divorced from everything that surrounded it: Google's place in the industry with regard to search engines, ads, etc.
replyIn this specific example there is a very big difference between producing a format for use in a first-party app vs trying to replace standards for content used across the web.
> And the technical implementation used can't be divorced from everything that surrounded it: Google's place in the industry with regard to search engines, ads, etc.
replyI mean... sure it could have? There could have been an independent "AMP Foundation" that forked the standard away from Google and owned the evolution of it from then on. Like how SPDY was forked away from Google ownership into HTTP2.
AMP was a good technical solution for a short window of time, deliberately tanked by confusing/centralized stewardship.
replyThey kept opening it more and more but by then it was too late.
No it wasn't. It was a tool to attempt to keep people on Google's surface area rather than freeing them to browse the web as the web was intended.
reply