4 ms·
It actually forces websites into good practices. Maybe not the absolute best, but most of the times, the AMP site is just better, or at least, faster. People u
by GuB-42 6y ago
It actually forces websites into good practices. Maybe not the absolute best, but most of the times, the AMP site is just better, or at least, faster.
People usually don't want a "full experience" when reading news. Especially when the "full experience" is pop-up ads and autoplaying video.
The bad part about AMP is that it is tied to Google services. But once de-Googled, AMP is really good 99% of the times, I leave 1% for those web designers who really use their skills to provide a better user experience, and do it right.
- sam_goody 6y agoAnecdotally, I disagree. Considering all the extra JS it requires to preload, I also question it from a practical standpoint. Of course, if you are otherwise including 3MB of JS for no reason, and it isn't cached, and you aren't using a CDN, maybe, perhaps, Google's CDN might serve it faster.. Though to be fair, I use FF, so AMP is hostile to it, and anyways FF has this great reader mode.. But do you have any numbers to back up the claims that any AMP pages are ever better?
- stetrain 6y agoYep, I actually like the idea of a narrow standard like AMP for fast loading content pages. The hosting/caching of those pages on outside caches is a bit more problematic, especially when it gets used by Google to de-emphasize the destination site in favor of flicking through Google results. I think the same idea implemented as a browser standard would have much better reception.
- Kalium 6y ago> The hosting/caching of those pages on outside caches is a bit more problematic, especially when it gets used by Google to de-emphasize the destination site in favor of flicking through Google results. I think this gets at a core tension - there are three parties involved in a search results page. The search engine, the destination site, and the user. Each has its own set of incentives. Both search engine and destination site have this bizarre idea that they have some kind of root-given right to the user's undivided attention for as long as they like. The user's interests are frequently poorly represented. They rarely include giving either search engine or destination site the amount of engagement each feels they deserve. Often, but not always, the search engine is somewhat better aligned with the user. > I think the same idea implemented as a browser standard would have much better reception. I personally have quite deep doubts. A standard like AMP works only because it can require adhering very strictly to a tightly written specification that blocks a lot of the things website authors want to do. I suspect AMP as a browser standard would produce a vast amount of forever broken webpages before publishers ditched it due to poor ad revenues and went back to their crappy, bloated, slow, ad-laden pages. The ability to load it into a CDN controlled by someone else - kind of a huge deal for performance reasons - is exactly the key feature that's user-friendly and hated by publishers. It's the kind of thing that would be cut out of a browser standard or just ignored by publishers.
- ryandrake 6y ago> The user's interests are frequently poorly represented. The user's interests should be looked after by the browser. A true "user agent" should act on behalf of the user's preferences, fetching only what the user says they need, and rendering it in a manner that the user wants, not necessarily how the web developer wants. We've gotten far away from this ideal over the years, with browsers ceding more and more control to web developers. Users have lesser and lesser say as to how their browsers render web sites, to the point where we now just have super-blunt instruments like ad blockers and "Disable javascript". If a web site is too slow, or choked with ads, or doesn't use an accessible color scheme, or uses a font too small, I want my browser to do something about it. I don't want to have to rely on the web developer (or Google) to adopt my own preferences. And if my browser even allows this, the function should be easy to use, not buried deep in Settings.
- Kalium 6y agoI think there's a mismatch here that only becomes apparent when you consider what level each web service and the browser are operating on. Search engines and publishers are considering intent - which is relatively easy because they have a small area over which to infer it. Browsers are operating as smart tools capable of interfacing but not capable of understanding intent because the scope of possibility is so broad. You're right. User agents should be for the user. They should expose options and controls for the user. They should tune and change and transform things for the user. They should understand what the user wants and make life easier for the user. I am just skeptical that browsers are ever going to be true user agents and capable of fully representing the user's interests and intent.
- MrStonedOne 6y ago> People usually don't want a "full experience" when reading news. But the question is do they want news sites to get promoted over the actual content they were looking for because news sites can be amped and dynamic content sites can not be amped?
- aardvark179 6y agoIt appears to consistently break zooming and reader mode for me on iOS. From an accessory view point I cannot wait for it to just die.
- deleted 6y ago[deleted]