6 ms·
I don't like AMP at all and fully agree with all the lock-in concerns - but I didn't find this post particularly convincing. This reads in places like a develo
by xg15 8y ago
I don't like AMP at all and fully agree with all the lock-in concerns - but I didn't find this post particularly convincing.
This reads in places like a developer or publisher who has grown accustomated to stuffing his pages with gobs and gobs of javascript and questionable UI patterns and is now outraged at the prospect that someone wants to take that privilege away from him. I can't agree with that.
Examples:
> The underlying message is clear: Google wants full equivalency between AMP and canonical URL. Every element that is present on a website’s regular version should also be present on its AMP version: every navigation item, every social media sharing button, every comment box, every image gallery.
So Google's suggestion is that, if you've already chosen to offer an AMP page, that page shouldn't have intentionally worse usability than the original?
> For years Google has been nudging webmasters to create better websites – ‘better’ meaning ‘easier for Google to understand’. Technologies like XML sitemaps and schema.org structured data are strongly supported by Google because they make the search engine’s life easier.
Other initiatives like disavow files and rel=nofollow help Google keep its link graph clean and free from egregious spam. All the articles published on Google’s developer website are intended to ensure the chaotic, messy web becomes more like a clean, easy-to-understand web. In other words, a Google-shaped web. This is a battle Google has been fighting for decades.
Sitemaps and structured data were the non-proprietary attempts to structure the web. Those could have made the web more accessible for everyone, not just Google. They are something fundamentally different than AMP.
Yet, he condemns them too? Why?
He seems to argue that the chaos and messiness of the web infrastructure is itself a quality that should be defended. Why would that be the case?
- unethical_ban 8y ago>So Google's suggestion is that, if you've already chosen to offer an AMP page, that page shouldn't have intentionally worse usability than the original? Google is using its dominance in search (again) to force sites to offer AMP versions. Like a "reader view", and lacking evidence at the moment, I bet many sites are building AMP versions with faster load times but reduced features to comply. Now Google is saying "Build your entire site according to our spec, or we'll de-rank you on search". That is a very bold move, and one that would be making front-page news if they said it straight-up in a way that Buzzfeed could write about.
- inetknght 8y agoI, personally, hate websites that serve different content based on what device I'm using. It makes it difficult to customize a device to view things the way I want to view them. All of the changes to navigation and features makes it difficult to navigate and use the site. I do think there could be a case made for Google abusing their power here but frankly I'm on their side for this: one site, one representation. If you want a lighter load for mobile users, provide a lighter version for every user. If you want to keep features available, allow users to opt-in or out to such features.
- xvector 8y ago> I do think there could be a case made for Google abusing their power here Which is the concern here. Abuse of power in order to push your own agenda could just as easily turn into abuse of power to push an agenda you despise.
- unethical_ban 8y agoI think you're ignoring the capabilities and UX that desktop can provide vs. mobile. You're essentially asking for what Ubuntu did with Unity and GNOME with... well, GNOME, in that they're shoehorning a mobile/touch UX into a desktop. That isn't always the way to go.
- bobthepanda 8y agoI mean, an even worse example of that would be Windows 8. Metro everywhere was a colossal failure. Hence the dialing back for Windows 10. There's nothing wrong with having different mobile and desktop experiences. Just make sure they have feature parity and behave in similar, expected ways.
- ehnto 8y agoI agree it's not ideal to have different experiences. But this wouldn't be true if Google didn't start imposing AMP through their influence. This has been an elaborate attempt to push everyone into a requirements system so that they can control how websites are built. Like an app store policy for websites. That's bad news, because their influence is real, businesses rely on search traffic to exist, and will have no choice but to comply.
- Izkata 8y ago> > The underlying message is clear: Google wants full equivalency between AMP and canonical URL. Every element that is present on a website’s regular version should also be present on its AMP version: every navigation item, every social media sharing button, every comment box, every image gallery. > So Google's suggestion is that, if you've already chosen to offer an AMP page, that page shouldn't have intentionally worse usability than the original? Take a moment to read that again. Mobile has constrained screen real-estate, constrained bandwidth, and navigation typically requires fingers covering the screen - and yet it's still supposed to support everything the full site does, and be more performant, and (it looks like) all be done in a particular framework? Google is talking crosswise, it's no wonder AMP is a pain that only benefits Google.
- ehsankia 8y agoI'm confused, I thought AMP was only for mobile (accelerated mobile pages). By regular version, don't they mean the regular mobile version?
- Izkata 8y agoSome quick searching to double check, it seems like not. Everything I see is referring to the "canonical" page, without really defining it in context. But based on the way you use it, the canonical version would be whatever the primary version of the site/page is, most likely the non-mobile version (among other things, this is the URL search results would send you to [0]). It all reads like the AMP version is supposed to replace the regular mobile version. [0] https://support.google.com/webmasters/answer/139066?hl=en#why-it-matters https://support.google.com/webmasters/answer/139066?hl=en#wh...
- ricardobeat 8y agoBoth sitemaps and schema.org had strong influence from what google thought worked best. Other open efforts like microformats and RDF died a cold, lonely death.
- coldtea 8y ago>This reads in places like a developer or publisher who has grown accustomated to stuffing his pages with gobs and gobs of javascript and questionable UI patterns and is now outraged at the prospect that someone wants to take that privilege away from him. I can't agree with that. Well, it's not your job to agree with that or not though. He should be free to do as he pleases (so, the freedom to spew gobs of JS etc. should be unarguable) and you should be free to not visit his page.
- ben_w 8y agoShould they be free to spew gobs of JS? The average person can’t tell in advance — or, often, after the event — that this will happen, and when it does happen it is bad for them. Aside from the security issues, the current status quo shortens battery life, wastes bandwidth (which is still precious and limited on mobile, even if not on landlines), and is generally done for the benefit of everyone except the user.
- coldtea 8y ago>Should they be free to spew gobs of JS? The average person can’t tell in advance — or, often, after the event — that this will happen, and when it does happen it is bad for them. If they can tell in advance, they can tell it after, and punish the page by not visiting it. If they can't tell it after the event, then it shouldn't matter.
- xg15 8y ago> If they can't tell it after the event, then it shouldn't matter. Ah yes, the famous strategy for solving all problems: Hiding them, because if no one notices them anymore, they are not problems anymore.
- coldtea 8y agoIsn't that the definition of empiricism and/or utilitarianism? If something doesn't impact someone in a way that they can ever tell, it is not a problem to them.
- deleted 8y ago[deleted]