Linked by Thom Holwerda on Thu 6th Sep 2018 23:34 UTC
Google

"People have a really hard time understanding URLs," says Adrienne Porter Felt, Chrome's engineering manager. "They're hard to read, it's hard to know which part of them is supposed to be trusted, and in general I don't think URLs are working as a good way to convey site identity. So we want to move toward a place where web identity is understandable by everyone - they know who they're talking to when they're using a website and they can reason about whether they can trust them. But this will mean big changes in how and when Chrome displays URLs. We want to challenge how URLs should be displayed and question it as we're figuring out the right way to convey identity."

Judging by the reactions across the web to this news, I'm going to have the minority opinion by saying that I'm actually a proponent of looking at what's wrong with the status quo so we can try to improve it. Computing is actually an incredibly conservative industry, and far too often the reaction to "can we do this better?" is "no, because it's always been that way".

That being said, I'm not a fan of such an undertaking in this specific case being done by a for-profit, closed entity such as Google. I know the Chromium project is open source, but it's effectively a Google project and what they decide goes - an important effort such as modernizing the URL scheme should be an industry-wide effort.

Permalink for comment 662080
To read all comments associated with this story, please click here.
RE: Let me resume this for you
by jh27 on Fri 7th Sep 2018 13:04 UTC in reply to "Let me resume this for you"
jh27
Member since:
2018-07-06

URLs (as originally designed) are human readable.

Google (and other culprits, ie PHP creators) have been f--king up the guidelines in their own benefit.

And now Google wants to, what, to "kill the URL"? Sorry, but no. You f--ked up your Search Engine with crappy refers, fix it, and leave the original URLs alive.

(Of course, with the exception by Berners Lee of killing off the "http://" and maybe transform it into "web:")


I'd agree with that. I find a lot of my URLs need fixing to remove https://...ampproject.com from the start of them. I love the fact that they provide zero indication of what they perceive the current issues to be or what the replacement might look like. Reminds me of how certain email clients improve they interface by showing the sender name rather than the email address.

Reply Parent Score: 1