Linked by Thom Holwerda on Sun 18th Apr 2010 11:57 UTC, submitted by Anonymous
Permalink for comment 419602
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



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?