Firefox 4.0 Goes Chrome, New UI In Q4 2010
sv_libertarian writes "Mozilla recently updated its product roadmap through 2010. According to the first draft, the current browser will see a minor update in Q4 2009 and another in Q2 2010. Version 4.0 is headed for an October or November 2010 release and will bring a new user interface and browser sync integration. 'There is not much information on [what] this new user interface will look like, but the first mockups that have been posted on Mozilla's website suggest that the Mozilla team favors a Google Chrome-like design that integrates Windows 7 graphics features. Overall, window elements seem to be floating over the background.' The mockup page emphatically notes that the design is not final."
DO IT, I use chrome for the UI, and love FF for the plugins, if they go with the tabs on top and no titlebar, if only as an option, I am back on board with them...
If there's one thing I hate about Chrome it's the way the tabs replace the normal title bar functionality. It makes the window harder to drag, harder to maximize, and basically throws 25 years of Windows usability standards out the window. I expect something like this from Apple but not from Firefox (or Google for that matter).
A nonstandard UI is the epitome of developer arrogance. The tabs-on-bottom mockup is excellent, but the tabs-on-top concept needs to die on the drawing board.
On the flip side, if Firefox 4.0 supports some of the new Windows 7 standards like Aero Peek controls I will be very pleased!
Am I the only person who thinks transparency sucks? If it's too transparent, the content can be hard to pick out from the background. And if it's only a little transparent (OS X), the menu can look like it got smudged with dirt. Are we expected to use only low-contrast, muted backgrounds?
If I wanted to see a partially obscured, blurry version of what's behind my browser, I can just smear my glasses with Vaseline and minimize Firefox.
I do have to say, what I really want out of a browser is function, not a flashier interface.
Make it not crash, and I don't care what it looks like.
"Form Follows Function". It's an eternal debate.
I'm of the team that says we can have both. Especially if they factor in software ergonomics into their design decisions. Most people don't realize it, but they like intuitive designs. Clearly, minimalism (an element of both form and function) is what is "in" for web-browser designs right now. We don't apparently need 8 menus with 20 submenus with 14 more sub-submenus, combined with 9 sections in the options menu, each with 15 subsections. We don't need 40 icons between the top of our web page and the bottom of our address bar.
So, you can have your function (a web browser with less junk crammed into it, and therefore a lower probability of things going wrong) and I can have my form (a nice looking, easy to use minimalist web browser). Everyone wins.
Why'd all the browser developers decide that this same model we have for browsing web pages is adequate? Considering how much time we, as a human race, are currently using the web browser, I would hope that we could make one that is a little better than this Netscape 26.0 shit we're stuck with. Apple, are you there? Can you please do for the browser what you've done for the phone? Google, we know you have like $n! dollars, can't you throw some more money at this problem? Chrome (which I am browsing from ATM) is pretty half-baked.
Shouldn't this thing read to me by now, standard? Shouldn't I have a better way to look at multiple pages than separate tabs and windows? Why does it all crash so much? Why must it be such an unelegant, awful thing to display information to from programming languages?
Long live the BSD license
I am not so sure that users actually care that much about standards and fitting into each desktop at the end of the day. If you have a feature they want users will use your application no matter what it looks like. A nice Example is Google Chrome. By default they paint their own window handles/boarders on X11 pretty much guaranteeing that it wont fit into any desktop. This is a case where they are going directly against having a native standard control, actually putting in effort to break it in the name of consistent branding* and users put up with it because they want to use Chrome. * From Ben Goodger: http://groups.google.com/group/chromium-dev/browse_thread/thread/b89ab99a0c848b89?pli=1
Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
The problem is that Slashdot is handing out moderation points like candy these days. They're becoming more Digg-like; maybe because their overloads have told them that the more traffic Slashdot gets, the better. Since Digg.com is a good deal more popular than Slashdot, maybe they're trying to emulate Digg more.
Personally, I prefer the older Slashdot where we didn't confuse "troll" with "legitimate criticism of Linux" or "Legitimate rebuttal of conservative idea". The reason Slashdot had moderation in the old days was to stop the brats who would post Goatse links and what not; it was not to stifle legitimate discussion.
MaraDNS is an open-source DNS server.
But a pain in the ass for tech support people over the phone who need to check browser settings... "File ?.. I don't have anything that says file..".. And then there are the off flavors of Xp, which has different locations for network settings.. bastards.
waiting for ad.doubleclick.net
I like having my Back, Forward, Reload, and Stop buttons left of the address bar. I can't believe they're considering adopting an IE-esque interface.
Their Chrome-like tab examples really fail, since they don't touch the top of the screen. That means not only are they not where you expected them to be, but you also can't click them by ramming your cursor to the top of the screen.
(This is a big one for me - I hate those X buttons that are in the top right, but are several pixels out, so that you actually have to look and see where your cursor is)
In short, I agree that non-native = bad. Windows has always had easy to click buttons, scrollbars, etc. on the edges - I hope they don't screw that up. ;)