Firefox 3.7 Dropped In Favor of Feature Updates
Barence sends in a report from pcpro.co.uk that says "Under its original plans, Mozilla would roll out Firefox 3.6 and 3.7 over the course of 2009, each bringing minor improvements to the browser. However, a steady stream of delays to Firefox 3.6 has rendered that goal unobtainable, forcing Mozilla to rethink its release. As a result, Firefox 3.7 has been dropped and will be replaced with feature updates for Firefox 3.6 that will be rolled out with security updates. This should free up the team to work on the next major release, Firefox 4, slated for the last quarter of 2010, which is expected to follow the same development process." Updated 20100116 00:54 GMT by timothy: Alexander Limi, from Firefox User Experience, says that the PC Pro article linked above misinterprets the situation, and that 3.7 is still on the roadmap before 4.0. The confusion stems from a schedule realignment: the out-of-process plugins feature, originally slated to land in 3.7, will instead ship as a minor update in Firefox's 3.6 series. According to Limi, CNET gets it right."
I admit firefox was a great program when it was first released and 2.0 was not too bad either. However, when 3.x came along Firefox became an unstable memory hog, moreso than Internet Exploder. In fact Firefox is too crash prone for my tastes. Even Shiretoko, the 64-Bit version of Firefox, is unstable and more crash prone than IE. What conclusion did Mozilla come to? Naturally it is either a feature or it is the result of plugins and addons. In other words they are taking the advice of Microsoft developers of the 1990s and they do not want to fix their problems. Until Mozilla gets around to fixing the fatal flaws in Firefox(which does not look likely in 3.x or 4.x) people should avoid Firefox like the plague and go for other solutions such as Opera, Chrome, Safari, or even Lynx.
You're thinking of moving to IE because you can't get tab previews in the taskbar? Man, that's weak.
Linux, you magnificent bastard, I read the fucking manual!
WPF user interfaces use XML. ECMAScript itself is no worse than Python; in fact, several people have called ECMAScript "Lisp with C syntax". (In that way, ECMAScript could be thought of as an M-expression language.) A lot of the public griping about JavaScript relates to different web browsers' interpretations of the HTML DOM spec. But if Mozilla controls both the XUL/XBL DOM and the script that goes along with it, that becomes not an issue.
What. The. Fuck? That's a lot of buzzwords, is completely unelated to my post. Go find your own thread, dude. This one's mine!
#fuckbeta #iamslashdot #dicemustdie