4 ms·
I think we have to participate. It claims to be an open standard; we should participate (or try to participate) in the open standard. The problems AMP solves
by paulddraper 9y ago
I think we have to participate.
It claims to be an open standard; we should participate (or try to participate) in the open standard.
The problems AMP solves are real. They will be solved one way or another. I'm hopeful they can be solved in an HTMLite sort of way, not a whatever-Google-does sort of way.
So let's think about how to improve AMP, change AMP, evolve AMP, until it becomes something else and something better than even its creators thought. Destroy it from the the inside.
EDIT: I know AMP has been terribly approached, and it might be nice if it just disappeared. I'm not claiming otherwise. But it's not going to disappear the same way proprietary LiveScript didn't disappear. I don't want to just scream at walls; we've been trying that.
- mulmen 9y agoThe best way to improve AMP is to drag it out behind the wood shed and shoot it. People just need to get better at making mobile web pages.
- paulddraper 9y agoI'm not saying you're wrong. But I will say I think your wood shed idea won't work. (Though I am very open to hearing more about it's implementation.)
- mulmen 9y agoYeah I don't think that's realistic either but validating Google by participating in their selfish initiative isn't going to do anyone any favors. Where you can oppose the adoption of AMP and work on improving the rest of the ecosystem so that AMP has fewer compelling applications.
- JoshMnem 9y agoAMP isn't truly "open" technology. You can't even discuss its problems on Github without getting the conversation shut down. AMP is an insidious threat the the open WWW itself. It doesn't solve problems that can't be solved in better ways.
- ocdtrekkie 9y agoI make this mistake too, but we need to stop calling it an open standard unless it's handed over to a neutral standards-making body. AMP's solution to the URL problem involves another Google-pushed web standard, webpackage. But the big difference is that webpackage is part of the WICG, a community group under the W3C. That's a real standard, this is not. If AMP not handed over to the W3C, I don't think we can or should call it a standard.
- indigochill 9y agoI'm not at all up on my tech politics, but I'm curious about your implication that the W3C is neutral. Is that something we can take for granted, given the way they went forward with EME[0]? Otherwise, though, I'm inclined to agree. [0] https://www.eff.org/deeplinks/2017/07/amid-unprecedented-controversy-w3c-greenlights-drm-web https://www.eff.org/deeplinks/2017/07/amid-unprecedented-con...
- ocdtrekkie 9y agoI'm definitely not fond of EME, but the W3C's interests go well beyond that of a single corporation. For instance, WICG, which I mentioned, lists three chairs, who are employed by Google, Mozilla, and Akamai respectively. I don't think Mozilla was super fond of EME either, but couldn't afford to be "the web browser that can't watch Netflix". I definitely do remain wary of these groups being forced to rubber stamp things, I do feel Google exerts way too much control even in that space, because due to their monopolies, they can just implement what they want, and sometimes the W3C has to accept it or be irrelevant.
- lern_too_spel 9y agoI want instantly loaded web pages now, not in 5 years when the standard is ready and Apple has finished dragging its heels and implemented it in its browsers, allowing publishers to finally use it.
- quanticle 9y agoThat attitude is what allowed Internet Explorer to become the dominant browser. What are you going to do when Google gets bored of supporting Chrome and disbands the team, leaving your web pages tied to a stagnating browser?
- mcguire 9y agoAm I reading the article right: the browser preloads resources from amp pages from the search page? That's going to be hard to fix in an HTMLLite sorry of way.
- tankenmate 9y agoHTTP/2 servers can preload (if they choose).
- dragonwriter 9y agoDoesn't that require same origin, and thus AMP-style central caching?
- lozenge 9y agoGoogle is pushing "HTTP origin signed responses" which will mean Google or any other implementing server can cache responses from other (willing) origins and push or offer them. Then, the address bar can show the actual origin, instead of www.google.com/amp as the origin.
- underwater 9y agoPreload is different from push.