Just like we have made silos on the mobile market, the internet will slowly get it's own silos. For people to value decentralization, they need to be shown direct and observable value. Just taking a moral/ethical stand is not enough. This is the case with anything and not just technology. The cars and the phones we use probably enslave chinese and kill polar bears.. but for all what the general population cares those things don't exist/happen. This comes down to human nature.
Google AMP Is Not a Good Thing
21–30 of 169 posts
Re: Google AMP Is Not a Good Thing
#22Out of interest, is there anyone who wants to defend the current Google AMP (not the concept of lighter webpages, but how google has gone about it?) I haven't found anyone yet personally.
1. I can click a link to an article from a search result
2. I can read the article without having to wait 5 mins for every little javascript and popup to finish
3. Success
Optimizing a rich content-heavy website is hard, and time consuming. While we all can moan about all the tracking and ads that appear on these sites, they are a fact of life, and simply relying on the engineering chops of every website to up their game is not a winning strategy. It's infinitely simpler at the end of the day to drop in a few extra scripts and meta tags than to yak-shave-optimize the entire site.
Re: Google AMP Is Not a Good Thing
#23Do we really need Instant Articles (Facebook) and AMP (Google) when we can accomplish fast loading pages with plain, uncomplicated HTML and CSS? I feel that many web developers don't realise that simple HTML and CSS is often all you need to make clear, fast loading pages. No complicated tricks or techniques required. You can make the page reasonably pleasant in appearance too. Think of the sites you often visit: news…
> Do we really need Instant Articles (Facebook) and AMP (Google) when we can accomplish fast loading pages with plain, uncomplicated HTML and CSS?
Can you suggest frameworks that help me do this automatically? Please no, raw html. I daresay that those would recommend developing without frameworks have no experience maintaining other people's projects.
Re: Google AMP Is Not a Good Thing
#24> The content loads off of Google’s own server, not from the website itself.
It seems the author isn't familiar with how CDNs work, how they've been around for many years and how they serve most of the data on the internet.
When you browse YT, the data most likely isn't being served by Google directly, but by a Google-provided rack on your local ISP.
When you browse a newspaper website, it is most likely coming out of an Akamai or some other CDN's server in your local ISP. Akamai by itself serves about 30Tbps of local traffic around the world.
And before these massive CDNs emerged, small ISPs would use caching solutions for static content (most of the web back then).
So we've all been loading content from 3rd party servers for more than a decade, not from the website itself. The internet as it is today is only sustainable because of CDNs.
Re: Google AMP Is Not a Good Thing
#25Out of interest, is there anyone who wants to defend the current Google AMP (not the concept of lighter webpages, but how google has gone about it?) I haven't found anyone yet personally.
As someone that dislikes viewing desktop sites on mobile devices I have no problems with AMP. It would seem the majority of people that have issues with it have to do with Google caching the content. If you don't like Google caching AMP content then host your own caching. It's free open source software.
This is software vs. services confusion. It's sort of like saying that if you don't like Reddit's moderation policies, host your own Reddit, it's free software.
Also, most people who complain about AMP claim that no caching is needed, just adherence to the AMP format. But there's no way to go from a Google search results page, or a link provided to you by someone who uses Google for search, to an uncached page.
Re: Google AMP Is Not a Good Thing
#26Google should reward fast / jank-free websites instead of rewarding websites that use one particular technology (AMP). On SERPs, both the "flash" icon and the AMP carousel are AMP-exclusive which suggests that Google is abusing its market power.
Bing also includes AMP in their search results: http://blogs.bing.com/search/September-2016/bing-app-joins-t...
AMP is a standard for creating fast / jank-free web sites, which all search engines can implement freely. Google is spearheading the effort because nobody else did, but they're not monopolizing it. Everyone is free to contribute.
Re: Google AMP Is Not a Good Thing
#27I remember when Google had a really awesome thing that provided great content experiences: It was called Google Reader. I wish they would take some of the energy they are using trying to force AMP down everyone's throats and just re-launch Reader.
Re: Google AMP Is Not a Good Thing
#28Out of interest, is there anyone who wants to defend the current Google AMP (not the concept of lighter webpages, but how google has gone about it?) I haven't found anyone yet personally.
Sure. AMP is a good thing. Google is simply the first company to implement the AMP cache-- Cloudflare has recently spun up their own and outbound links from Cloudflare-enabled sites can use an AMP cache that doesn't rely on Google, so they get the speed benefits as well.
The implementation of AMP is one of those technologies that's "the more it gets deployed, the better it is." Reading the spec, it's clear that Google's vision is for AMP to be the opposite of FB instant articles; where the entire web can have a decentralized cache (yes this sounds weird but makes sense). I suspect Cloudflare will help quite a bit with this.
I could see mobile networks implementing their own AMP caches, so their inbound traffic winds up terminating mostly at the cache layer. This speed boost will win the mobile networks customers.
Re: Google AMP Is Not a Good Thing
#29Do we really need Instant Articles (Facebook) and AMP (Google) when we can accomplish fast loading pages with plain, uncomplicated HTML and CSS? I feel that many web developers don't realise that simple HTML and CSS is often all you need to make clear, fast loading pages. No complicated tricks or techniques required. You can make the page reasonably pleasant in appearance too. Think of the sites you often visit: news…
> Do we really need Instant Articles (Facebook) and AMP (Google) when we can accomplish fast loading pages with plain, uncomplicated HTML and CSS? Can you suggest frameworks that help me do this automatically? Please no, raw html. I daresay that those would recommend developing without frameworks have no experience maintaining other people's projects.
We need it like we needed "use strict" in JS, which is to say not really, but it really helps. I think of AMP as "HTML Strict", a means of enforcing the rules and practices necessary for faster web sites.
Re: Google AMP Is Not a Good Thing
#30Do we really need Instant Articles (Facebook) and AMP (Google) when we can accomplish fast loading pages with plain, uncomplicated HTML and CSS? I feel that many web developers don't realise that simple HTML and CSS is often all you need to make clear, fast loading pages. No complicated tricks or techniques required. You can make the page reasonably pleasant in appearance too. Think of the sites you often visit: news…
We're not talking about developer/technical blogs, which are generally very lightweight, and the person making it likely takes pride in things like efficiency. Your typical content publishing platform on the other hand, is a giant mess of wordpress plugins, tracking, ads, and scripts that pull in other scripts that pull in other scripts. Is it efficient from a technical perspective? No, but it gets the job done for them. AMP is a solution that makes it dead simple for these shops to get a reasonable load time for their content on mobile, which translates to less time spent, which at the end of the day is more important to them.