Hacker News Reader

Comment by soared | Hacker News Reader

Why does this matter? Users don't care and its easier to remember/understand that all websites are just "x.com" rather than sometimes being "www.x.com". If you have some server/troubleshooting/network/dev problem with it, the missing info should be moved to developer tools.

This is just removing data that is useless and confusing to 99.9% of users - whats the problem?

View on HN

Because they are on www. and not *.

What happens when you copy and paste that URL?

Now every single website that wants to support Chrome needs to ensure that https://foo.com is always redirected to https://www.foo.com, or at least works as if it's www. It doesn't matter that most websites already do this, it's not standard, and represents Google breaking standards because they are big enough to do their own thing.

It's just one of the 1000s of papercuts that google is inflicting to keep users from switching web browser.

When you copy and paste, it has the whole URL - just like when you copy and paste now it will include http(s)://

What if you visually copy and paste? Parent is right.

One more reason to set up a redirect from or to www.

Many MANY legacy sites serve different information at those two domains.

And this is wrong.

Maybe you have a niche target and not looking for mass adoption. It's not "wrong" it's just not normally the way things are done.

the "www." still gets copied when you copy the full address bar just like the "http(s)://" before 69.

i’m a user too

Reply on news.ycombinator.com