8 ms·
The Two Faces of AMP
- lukestevens 9y agoThe particularly gross thing about the AMP project is Google's abuse of the concept of open source to recruit volunteer technical labor to implement their anti-FB corporate strategy. It's just corporate astroturfing. AMP is obviously conceived, funded, and implemented by Google and its employees. If you squinted your eyes and tilted your head just right you could see a "good for the web" angle with faster mobile pages. But AMP for email & AMP Stories have nothing to do with making the web faster, it's just another part of Google's attempt to essentially fork the web & control the platform so they can compete with Facebook by shoehorning FB/IG/Messenger features on to the web (Instant Articles, Stories, Carousels, "interactive" email etc). That's bad in and of itself, and for Google to present its corporate strategy as an "open source" project so it can enlist the help of volunteers and those passionate about the web is disingenuous in the extreme. There are far more worthy projects that could use volunteer help than a $750 billion company's corporate strategy. Further thoughts here: https://twitter.com/lukestevens/status/963905898895699968 https://twitter.com/lukestevens/status/963905898895699968
- refulgentis 9y agoIf only I had a nickel for every online commenter who swore up and down that no one else implements or supports AMP, and then uses that to justify claiming Google is trying to fork the web...all major platforms pursuing end-arounds mobile ad garbage, _except_ Facebook and Apple, use and contribute to AMP. Anyways, I'm just happy to finally have usable web results on mobile.
- ocdtrekkie 9y agoPeople's participation in AMP isn't voluntary. They have to implement and support AMP, or they get penalized by Google Search.
- deleted 9y ago[deleted]
- Jyaif 9y agoBing, Cloudfare.
- nine_k 9y agoThey sure exist! But Google's search has like 4/5 of the market. If you optimize for the bottom line (as a business should), what will you pay most attention to?
- JeremyBanks 9y agoI think his point was that Bing implemented AMP voluntarily, without being pressured as you suggest publishers were: https://blogs.bing.com/search/September-2016/bing-app-joins-the-amp-open-source-effort https://blogs.bing.com/search/September-2016/bing-app-joins-...
- ocdtrekkie 9y agoBing's primary pressure is a need to compete performance wise with Google. The fact that the implementation is bad doesn't mean they don't need to match on the metrics.
- so33 9y agoTo play devil’s advocate: the reason Bing can implement their own AMP cache and conform to AMP pages so easily is because AMP is an open project.
- ocdtrekkie 9y agoNobody said the problem was AMP's code being available. The issue is the way Google is forcing their framework's dominance using their search monopoly.
- dragonwriter 9y agoAnd Facebook only isn't participating because they are instead doing the same thing in a less-open way with Instant Articles.
- lukestevens 9y agoWho conceived of AMP Stories? Who conceived of AMP in Email? What do they even have to do with "Accelerated Mobile Pages"? My irritation with AMP is also driven by the fact it's not usable for me. Reader mode is often broken in iOS which is a particularly egregious regression. URLs are obviously broken. And sometimes sites can't even get text-on-a-page right with their AMP versions: https://twitter.com/lukestevens/status/963910460796936192 https://twitter.com/lukestevens/status/963910460796936192
- guelo 9y ago> finally have usable web results on mobile. Weird, I've been reading web results on mobile for over a decade.
- nixpulvis 9y agoAMP makes it faster (maybe) but the experience is worse. I copy URLs a lot to share, and a fucking AMP link doesn't even navigate and requires a different means of finding the actual URL... garbage.
- ravenstine 9y ago> AMP is obviously conceived, funded, and implemented by Google and its employees. If you squinted your eyes and tilted your head just right you could see a "good for the web" angle with faster mobile pages. An idea predicated on a lie can only go downhill. Engineers need to, as best they can, convince product owners that AMP in any form is a poison apple.
- tyingq 9y agoI wonder if Google's AMP team is truly drowning in the Kool aid or if they actually know what's going on, but keep quiet for job security reasons.
- jacquesm 9y agoYou should read back on some of the older threads here on HN where AMP is heralded as the best thing Google has done in a long time.
- tyingq 9y agoI have, but the comments I read were from the AMP lead, who I assume has fully drunk the Kool aid since they probably signed up for that job. I'm more curious about his/her team members. Google hires smart people. I assume they are free thinkers. Edit: I'm pretty vocal in those old threads calling out AMP as a walled garden play, FWIW. I remember AOL's early days.
- jacquesm 9y agoSmart people with mortgages at valley rates seem to get a lot less smart when they are looking at their own contributions.
- TrickyRick 9y agoDoesn't the valley work much like every other tech hub in the world, i.e. if you lose your job in the morning you can start a new job somewhere else sometime after lunch? Especially with a place like Google on your resumé.
- skybrian 9y agore: "abuse of the concept of open source to recruit volunteer technical labor" I'm pretty sure any programmers working on AMP at this point have heard the criticism (since it's repeated every time AMP comes up) and know what they're doing. They just disagree.
- ebbv 9y agoI would wager most programmers implementing AMP don’t feel they have a choice. Either they need to do it for SEO purposes or they need to do it because project managers say so it for SEO purposes. That’s kind of the whole reason AMP is bad.
- skybrian 9y agoThe grandparent was criticizing people who contribute to the AMP open source project. Even if it's getting a bug fixed to make your own site work, would it be better for it to be closed source?
- gcb0 9y agowhy do you think they are not the same? only contributed because my employer was lockedin into using AMP for the perverse SEO incentive.
- lukestevens 9y agoI understand people can contribute with their eyes open; that's fine. People volunteer bug reports (for e.g.) to paid software all the time, open source or not. My criticism was actually of Google soliciting those contributions in the first place. "Open source" is just a useful fiction in this case: what would a fork of AMP even do? It does however make the project corporately palatable to others that might want to implement it (i.e. Microsoft/Bing), plus it attracts unpaid contributions to fix the work of Google's highly paid engineers ("Building the future web, together."). The former might be necessary but the latter is extremely problematic IMO. Google could have set up AMP as an independent W3C group (for e.g.) at arms length from its competitive interests, but it didn't, and recent AMP product announcements show us why.
- JoshMnem 9y ago> If you squinted your eyes and tilted your head just right you could see a "good for the web" angle with faster mobile pages. AMP is much slower if you don't allow your browser to load JavaScript from 3rd party sources. It literally takes 8 seconds for my browser to display AMP pages. (Try it if you don't believe me.) AMP is also slower than optimizing it yourself.
- kurthr 9y agoI dream of 8 seconds :^) Really, I regularly get broken links on an android phone from Google News. It's hilarious to watch it try and resolve, if the article is more than 15min old. A direct link to the article just works. New links work. I'm guessing it's something similar to what you describe...
- Shoothe 9y agoI also experienced White Screens of AMP Death where only the AMP header was visible, not the page content. For what it's worth the white screen loaded pretty fast :)
- nixpulvis 9y agoThe basement dream of the web is dying faster and faster. At the hand of large, scared companies. It's ironic that the more powerful you get the more scared you become.
- paulddraper 9y agoThe phrase "nothing to lose" comes to mind about the fearless.
- nobleach 9y agoIt will never be okay to give preferred treatment to those that use your framework. This basically is telling all other framework authors, "never mind, Google has decided the one that anyone that everyone will have to use (if they want in to the SEO club)" At this point, they're no longer saying, "we've found the most pertinent search results". Instead, they're saying, "our friends provide the best stuff... don't bother looking at the others"
- throwaway_54321 9y agoAt what point do the people working in tech come to the realization that Google has become a problem that must be eliminated if the web is to continue to flourish?
- throwawaymaroon 9y agoall we can do is stand on these street corners with our signs
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- subhajeet2107 9y agoAMP implementation also sucks, why cant i use !important in css for AMP ? Also try to convert any user generated page to an AMP page and have fun with all the validation errors. AMP might be a good thing for web in general but the way it is handled poorly by google , atleast Facebok Instant Articles dont have that many restrictions
- seanwilson 9y ago> The letter calls on the AMP team to make two primary changes: > Instead of granting premium placement in search results only to AMP, provide the same perks to all pages that meet an objective, neutral performance criterion such as Speed Index. Publishers can then use any technical solution of their choice. How would you measure this in a way that couldn't be gamed? I'm not saying AMP is the best solution, but the way AMP prevents you from doing things that hurt performance makes it much easier for you to know for sure an AMP page has certain performance properties.
- tkadlec 9y agoFirst off, you're right: any metric can be gamed. Even so, Google is already using performance to factor into its algorithm, so some level of reasonable accuracy must have already been agreed upon. Ensuring a certain level of performance is not a very easy problem to solve. But it's doable. Myself and a few others sat down with the AMP team awhile back and chatted about what that would look like and there were definitely a few different layers that would be needed to get it to work. The first is already in progress. There's a spec for something called "Feature Policy" (https://wicg.github.io/feature-policy/ https://wicg.github.io/feature-policy/). Feature Policy would let you tell the browser you don't need certain features which would in turn let browsers take shortcuts (so to speak). For example, you could declare that you will not be allowing document.write. Enough features being declared could serve as a way for Google (and others) to say "Ok, this is going to be reasonably fast." There's more needed of course: we had discussions about a standard related to declaring a limit on asset sizes, etc. But it's a start. And while it will always be a little fuzzy, the same is true of AMP. It's completely possible to build a slow AMP page. The best Google can do is say "if they're doing X, then the odds are good that it's performant".
- seanwilson 9y ago> Ensuring a certain level of performance is not a very easy problem to solve. What I'm getting at is maybe AMP is Google's way to make the problem easy. Sometimes when a general problem is difficult, you're better adding restrictions to make the problem tractable. > It's completely possible to build a slow AMP page. Can you elaborate? How easy would it be to test AMP pages for that?
- djhworld 9y agoGoogle have to answer to shareholders, it's in their interest to keep users within their ecosystem.