Linked by Thom Holwerda on Sun 18th Apr 2010 11:57 UTC, submitted by Anonymous
Google Now this is something that I find really interesting. We all know and love Google Chrome/Chromium (and if you don't, you're demonstrably wrong), but Google recently made a change in the developer version that ruffled some feathers: the URL field will no longer show the "http://". This made a lot of people very upset.
Permalink for comment 419602
To read all comments associated with this story, please click here.
Comment by antwarrior
by antwarrior on Sun 18th Apr 2010 14:50 UTC
antwarrior
Member since:
2006-02-11

Honestly, I do not find this a big deal at all. Many of the arguments against this claim that it doesn't feel right or that users aren't that dumb etc. These arguments from what I have seen so far fall on the side of disrupted familiarity or on the side of unnecessary usability. At a minimum a browser should be able to understand the other protocols but it owes them nothing more than a nod or recognition. I might even go as far as to say, at the risk of sounding a bit radical, that the browser should only just be used for browsing web pages and that the other protocols do not necessarily have a place in the browser. That being said it follows that the "http://" portion of the url really does not carry any information at all to the user. The only time you might need an protocol indicator is if you are handling something different from http like ftp. Https already has a lock icon. Personally I do not understand the fuss. ... Can someone please give me a compelling reason to keep the text that indicates the protocol in the address bar?

Reply Score: 2