Google Wants to Kill the URL
wired.com
wired.com
There's no reason a well-behaved web sire (or application) needs to have a complicated URLs, that's just bad design. No need to scrap the entire concept of URLs because some people use it improperly.
Getting rid of the thousands of ugly URLs used by their own products could also go a long way...
Using HN as an example, what would the nice URL look like for this page?
The prime candidates for URL deuglification would be sites like amazon.com: https://www.amazon.com/Bushnell-Falcon-133410-Binoculars-Bla...
I mean, what the hell are all those identifiers, and why should anyone besides amazon.com's internal staff even see them?
https://www.amazon.com/Bushnell-Falcon-133410-Binoculars-Bla...
which is basically the product name + model number + asin
ASIN: https://de.wikipedia.org/wiki/Amazon_Standard_Identification...
Link can also be shortened to just the asin. (ASIN = ISBN applied to everything)
Still, Amazon is far from the worst offender. I have seen kilometer long URLs that can span several lines of text.
Or randomizes tracking codes!
For example, allow websites to customize how the URL is displayed. Every website nowadays has breadcrumbs. Let them put them in the URL instead. Let them provide icons and dropdowns for segments, but still allow users to change, copy and paste the raw URL (like the Windows file explorer).
All POST, all the time?
Seen versions of that. No, thanks.
Just hide the address bar?
We already quasi have this, where people just type what they want into a Google search.
And if Google doesn't list it prominently, they are at a loss and/or use some other site, instead.
People used to be totally overwhelmed by security. You know what? When it started to impact them, personally, they learned. I'm continually surprised by the conversations I now hear around me, by "normal people".
The URL isn't "too difficult". It's that people don't care about it. And "tech" keeps trying to hide it further.
I think a simple improvement would be to bolden the domain name in a URL.
Browsers could also add some styling to hyperlinks indicating whether they are to the same domain, to another domain that user trusts (for example because a login cookie has been set on its domain), but I expected diminishing returns on that. Even if it can be done reliably from a technical point of view, users won’t learn to discriminate multiple kinds of links.
They already did that. If you open Chrome right now, you'll see that the non-domain part is greyed out. It doesn't help much.
Most people don't go to addresses; they go to sites. In other words, people don't care about putting that "https" before they visit Facebook; they want Facebook and know that typing in "facebook.com" gets them there
Additionally, most of today's browsing isn't even done by web browser; it's done through mobile apps. That's why Apple wants to make the iPad the primary computing device; they already have a market-leading position on apps, so once iPads become the way that people compute, the efficacy of web browsers greatly diminishes
Additionally still, Chrome sets itself up to use Google as its primary search engine. Thus, if I type "facebook" into the search bar, the first result is almost always what I want (facebook.com). As well, Google (and other search engines) already do crazy-accurate location-based and context-aware searching so that they know that typing "ford" in Akron, OH likely means "ford.com" and typing "ford" in Toyko likely means "ford.co.jp."
So it makes sense for Google to think "What if people just typed the name of the thing they wanted without having to worry about whether it needs "https" or if it's a .com or a .org? What if objects on the internet can be located via some other means?"
[1] https://www.youtube.com/watch?v=7TwrABEAfTk - 7m30s