If it meets that schedule, Mozilla could crank out Firefox 6 just two months later.
http://www.pcworld.com/article/224795/w ... k.rss_news
Anonymosity wrote:Looking ahead is fine, but these guys lately have been copying others. Chrome has done away with menu bars and status bars, so Mozilla has to do that too. Safari and IE moved the reload button to the right end of the address bar, so Mozilla has to do that as well. Opera, Chrome, and IE (so I am told) have dumbed down the addressfield by greying out everything but the hostname (and sometimes the prefix of that), and the developers have been thinking about doing that as well, according to some comments on the Mozilla newsgroups. Where did people get the idea that the prefix of a hostname is not important, anyway?
James wrote:Look... it's all part of a smart business model. You can accuse them of "copying" but that is the reality of how business is done today. Firefox is infinitely customizable so you have the option of moving buttons wherever you choose to locate them. Chrome, Opera and IE have not "dumbed down" their address fields at all. The expression "dumbing down" is a very poor choice of words. In truth, the former way was more of a cluttering up of the screen. We don't need a myriad of buttons, address and search fields, bars for everything and anything in order to surf the internet. Firefox has not yet combined their search engine field with their address bar AND THEY SHOULD in my opinion. It's old school to leave it over at the side. My wife likes to surf with apps pinned to her task bar and so she chooses to use IE9. I don't care for that and so I choose to continue with FF and I use their bookmark bar. I don't like the idea of pinning sites to tabs because this simply takes you back to your last session rather than simply back to the site itself. In other words, in my view it is not as efficient as the MS idea of pinning a site and/or app to the task bar. Thus, I choose to use the bookmark bar and thereby can readily go to my favorite sites.
"The first Aurora release is still labeled as version 4.2a1pre and is not likely to change its version number to version 5.0 until it will go into beta on May 17.
Anonymosity wrote:That is the problem with trunk builds. They are extremely experimental, and you never know what is going to be broken. I tried the bleeding edge builds for a while, but they were too frustrating. Branch builds for Windows have the worst bugs fixed, and they work for the most part.