5 ms·

Google introduced AMP, and were eager to eventually have the whole web forced through their infrastructure without it being obvious. Shortly after, they starte

Google introduced AMP, and were eager to eventually have the whole web forced through their infrastructure without it being obvious. Shortly after, they started hiding www, and openly said that they intended to eventually hide the amp prefix as well - which would help their own goals. "www." was never a mistake that needed to be hidden, any more than any other subdomain. I bet that if Firefox had 90% market share and decided to hide the "translate" or the "maps" of maps.google.com, that Google would not find any justification amusing. www is a subdomain, and if a dev doesn't think it should be there, he could just avoid using it. It opens security issues (by showing the "wrong" URL), usability issues ("read me the URL letter by letter"), and it forces developers to deal with a incorrect setup that can change any day. What if Google then hide "app." or "dev."? But Google does what is best for Google.

jimmygrapes 5y ago
Yet nobody seems to have a problem with Cloudflare...
- deleted 5y ago
  [deleted]
- glaucon 5y ago
  What is it that Cloudflare does that is similar to this ?
  - sam_goody 5y ago
    I assume he meant that AMP was essentially a CDN, which meant that Google would be hosting the web on their edges, which is similar to what Cloudflare an other CDN's are doing on their edges. And there is truth to be afraid of Cloudflare. However, that is somewhat of "an appeal to hypocrisy". The obvious difference is that Google harvests all the data and usage and combines it with other data to profile all of your site's visitors. Cloudflare is not in that market, and even if they were they don't have the other pieces to combine it with. But, even leaving that out, Google did its best big bully act to show how much they don't care about you with their CDN, which is totally different than Cloudflare: They required you to modify your site - and even make it slower with heavy opaque scripts - so that they have more control than you do, they abused their search monopoly and the browser monopoly to force you onto their CDN and hurt competing CDNs, they set the guidelines of what resources and how you can send through the CDN (vs CF)...
fragmede 5y ago
www stands for world wide web so if you're looking for www with a web browser over that new fangled thing called the Internet, it's redundant.
- hwc 5y ago
  That is a problem to be fixed by the server, not the client.
smashed 5y ago
One of my pet peeves against chrome's URL is how it breaks copy paste. Sometimes you just want to copy the domain portion of the URL, without the hidden parts (scheme, subdomain).. You think what you select is what you copy? Wrong, Chrome is "smarter" than you and you end up pasting the entire URL, that you did not even see! Their design meant they had no choice but to break one use case or the other. Either you'd copy an incomplete, invalid URL meant for display purposes, or one containing chars you did not select. Bad UX either way..
vgeek 5y ago
I assumed this was a step in conditioning users to search for the brand (and maybe click on the brand's ad, or a competitor's, instead of the organic listing halfway down the page) instead of navigating directly. They don't even have a chance to make anything when you type in a domain name directly. AOL keywords v2.0.

jimmygrapes 5y ago

Yet nobody seems to have a problem with Cloudflare...

deleted 5y ago
[deleted]
glaucon 5y ago
What is it that Cloudflare does that is similar to this ?
- sam_goody 5y ago
  I assume he meant that AMP was essentially a CDN, which meant that Google would be hosting the web on their edges, which is similar to what Cloudflare an other CDN's are doing on their edges. And there is truth to be afraid of Cloudflare. However, that is somewhat of "an appeal to hypocrisy". The obvious difference is that Google harvests all the data and usage and combines it with other data to profile all of your site's visitors. Cloudflare is not in that market, and even if they were they don't have the other pieces to combine it with. But, even leaving that out, Google did its best big bully act to show how much they don't care about you with their CDN, which is totally different than Cloudflare: They required you to modify your site - and even make it slower with heavy opaque scripts - so that they have more control than you do, they abused their search monopoly and the browser monopoly to force you onto their CDN and hurt competing CDNs, they set the guidelines of what resources and how you can send through the CDN (vs CF)...

fragmede 5y ago

www stands for world wide web so if you're looking for www with a web browser over that new fangled thing called the Internet, it's redundant.

hwc 5y ago
That is a problem to be fixed by the server, not the client.

smashed 5y ago

One of my pet peeves against chrome's URL is how it breaks copy paste. Sometimes you just want to copy the domain portion of the URL, without the hidden parts (scheme, subdomain).. You think what you select is what you copy? Wrong, Chrome is "smarter" than you and you end up pasting the entire URL, that you did not even see! Their design meant they had no choice but to break one use case or the other. Either you'd copy an incomplete, invalid URL meant for display purposes, or one containing chars you did not select. Bad UX either way..

vgeek 5y ago

I assumed this was a step in conditioning users to search for the brand (and maybe click on the brand's ad, or a competitor's, instead of the organic listing halfway down the page) instead of navigating directly. They don't even have a chance to make anything when you type in a domain name directly. AOL keywords v2.0.