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 419615
To read all comments associated with this story, please click here.
Let them play
by eazel7 on Sun 18th Apr 2010 15:51 UTC
eazel7
Member since:
2007-09-09

1) It's just in the dev channel, it might not get to the release

2) If it's not in some channel no data could be gathered about its usage, maybe it's a great idea and we can't see it

3) If you have mangled corpses, there are two problems: they're not nice and they're not healthy. One is solved a-la-apple by hiding them. The other one is solved by removing them. If you can't remove the corpses yet, please hide them because they're so disgusting that I might puke.

4) http(s):// schema is not a mangled corpse, it's a rockstar. It's the core protocol of a browser. It was so damn good that it conquered the entire web space. ftp:// gopher:// or whatever are strangers in the browser world. What is the ratio usage of http(s):// vs other:// in a Chrome Browser? I'm sure about how small the percentage will be...

5) Don't think about 'the IT Pro', 'the dummy user'. It's about humans.

Note beside: If you make things *less simple* that what they can be, you're missing something. And if you make them complex, people will not understand and that will upset everyone.

Reply Score: 0