4 ms·
A lot if big words disguised as good intentions. There’s nothing fast, instant, or open about AMP. The latest article debunking those myths: https://ferdychri
by dmitriid 9y ago
A lot if big words disguised as good intentions.
There’s nothing fast, instant, or open about AMP.
The latest article debunking those myths: https://ferdychristant.com/amp-the-missing-controversy-3b424031047 https://ferdychristant.com/amp-the-missing-controversy-3b424...
Google’s fully opaque process around AMP for email (yes, it’s a thing): https://github.com/ampproject/amphtml/issues/13597 https://github.com/ampproject/amphtml/issues/13597 and https://github.com/ampproject/amphtml/issues/13600 https://github.com/ampproject/amphtml/issues/13600
- ocdtrekkie 9y agoThe fact that Malte is still trying to call the AMP project "well-lit" is really what throws a lot of question on this blog post. AMP is not a "well-lit" project. Why not hand AMP itself over to standards groups as well as all of the other things mentioned here? What about the proprietary GMail implementation of AMP4Email? Or the fact that none of the justifications for AMP given in this (or The Verge interview[0]) hold up as reasons for AMP4Email. [0] https://www.theverge.com/2018/3/8/17095078/google-amp-accelerated-mobile-page-announcement-standard-web-packaging-urls https://www.theverge.com/2018/3/8/17095078/google-amp-accele...
- skybrian 9y agoHanding over AMP would prevent the standards committee from making backward-incompatible changes to please other participants. It seems better to start fresh and have a compatibility break? Not to mention that there's little point in preserving a name that's pretty controversial. And in the meantime, AMP would still need to be maintained. We've seen this before in less controversial areas. For example, SPDY was proprietary and HTTP/2 is a standard that entirely replaced it. I'm wary of AMP4Email as well, but the process of doing something quick and dirty and then standardizing the 2.0 version (under a different name) is pretty common.
- ocdtrekkie 9y agoGoogle is not replacing AMP, or promoting the standards group to replace AMP. Google is using things like web packaging with AMP, and intends to continue to do so. Their statements today, if anything, state a clear intent to continue to invest in and build on AMP. So, while all of these other components are going to be going to standards orgs, why not let them also have AMP? (A standards org is never beholden to keep an existing standard, they can always make a new one.)
- dmitriid 9y agoMoreover, if you read their proposed “standards”, you can see how they want to just have the same AMP treatment for other pages. iframe promotion explicitly describes how AMP pages become “fast” (through preloading on Google Search pages) web packaging is just a way to have signed pre-rendered pages on a CDN. Together they give Google the power to cache/promote/“speed up” pages at will
- cromwellian 9y agoNo, together they give anyone aggregating content to do that, and they allow CDNs to serve up top level content with the original domain intact. So much noise in these threads deliberating trying to concoct some hidden agenda around this rather than the obvious: the mobile web was a looming disaster, years of people advocating for writing fast pages failed, to the point that native apps were becoming silos to serve proprietary news content from. All of the macho-code jockeys here boasting how they can write fast pages don't seem to get that like 100 million pages out there are slow as molasses and efforts like AMP manage to fix A LOT of load issues that independent super-hackers didn't. Independent efforts to spur people to optimize their sites and get some loading consistency failed -- multiple times. An industry wide effort is needed that deliberately pushes those, by carrot or whip, to improve the situation, giving them a cookie-cutter formula -- a subset of HTML and structure, validated for optimum parse, render, and caching, so that it is easy and consistent. AMP was the first attempt at this. People don't like it because it's proprietary, don't like the UI choices, ok then, let's rectify that and get the W3C and browser vendors on board to have a neutral version. Let's address all of the problems and criticisms and make a public standard. But stop pretending that if no one does anything the problem will go away. Yes, eventually it will go away, as more and more websites are replaced by native apps or embedded viewers in messaging or social apps like FB or WeChat, which become new proprietary browsers that eschew the web. Accusing the AMP guys of ulterior motives is really wearing thin, AFAIK these guys love the web with a passion, they're trying to fend off an assault from native platforms. Most of these guys could go work on new hot-news at Google like new machine learning projects, they could have their pick of work, but have dedicated a lot of effort to make faster, a platform that a lot of people don't care about anymore and view as legacy. How about a holding your gun-powder for once and see what comes out of this rather than setting off nukes.
- Ajedi32 9y ago> AMP is not a "well-lit" project. How so? As the blog post points out, the whole thing is open-source with almost all discussion surrounding the project happening out in the open on their GitHub repo. You might not agree with the direction the project is going, but I'd say it's about as well-lit as any open source project can be.
- ocdtrekkie 9y agoIt seems like that until you start asking questions. Then you discover that AMP4Email is controlled by Gmail team, that you can't get a straight answer to save your life, and when they don't like the topic, they subtly threaten the Code of Conduct when no violations are occurring to indicate they are actively searching for an excuse to close down discussion.
- lern_too_spel 9y agoAMP4Email has nothing to do with AMP as a validatable preloadable subset of HTML and the web packaging standard discussed in this article.
- pathseeker 9y agoPosting some discussions in the open doesn't make it well-lit. There are many projects following this path where the real decisions are made in private meetings by people in the controlling companies. Open washing is not open source.
- ocdtrekkie 9y agoIndeed, while discussing AMP4Email, it seemed that, despite being a proposal in the AMP Project, all decisions for it's implementation were already made (and committed to) by the Gmail team, it had already been "reviewed" by a security team (although any such security protections are limited to Gmail's own internal protections, other implementers are on their own), and there seemed to be no opportunity for the greater email community to comment before these things were decided. Having it up on GitHub after that doesn't really mean much. This is the same for Android and Chrome, of course.
- dmitriid 9y agoHello, Google’s AMP team. I see you’ve been busy downvoting my comment ;) Too bad you spend most of your time running away from uncomfortable questions and defending your overlord’s increasingly dubious and morally questionable practices.
- sctb 9y agoPlease don't break the guidelines like this. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html