Slashdot Mirror
Firefox 7.0 Beta Released
An anonymous reader sends word that the first Firefox 7.0 beta has been released. One of the big areas of focus for this version will be performance enhancements. One optimization "Reduces memory use and improves performance areas including responsiveness, startup and page load time, even in complex websites and Web apps." Another addresses one of Firefox users' long-standing gripes: "The JavaScript garbage collector works more frequently to free up memory and improve performance when you have many tabs open or keep Firefox running for a long time."
Next in few mins...Firefox 8 Alpha released and Firefox 9 Preview released... Do we need to clog up the front page with these articles? Gone are the days of version numbers making any sense in FF. We don't report Chrome versions do we?
This space for rent.
Not in the summary is an opt in feature that will report your memory use (presumably along with what pages you are on and extentions you are using) back to Mozilla so they can finally put the "but FF using 2 GB of RAM on my machine" bugs to rest, either by fixing them or by dispelling the myth depending on which is the case.
If the garbage collected collected leaks, they wouldn't be called leaks anymore.
This space for rent.
Firefox 7.0 has already reached end-of-life at the time of this posting...
Yeah, but the point was you knew right away 3.6 was nearly identical to 3.6.1 (well, should be anyways) and was probably pretty similar to 3.5, but not to 4.0. Now, you have no clue if 7 represents a major change or just a bugfix without actually testing it. Hence, frustration for developers. Mozilla is basically giving them less information about what the release cycles contain, and for no good reason whatsoever. And that is why people complain.
"None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
It's more that the beta for 7 comes out pretty much the instant 6 is released. One of the more interesting aspects of the Mozilla development process is that they essentially have a pipeline of four "releases" going on at once: Current (stable stuff, now 6), Beta (code being stabilized, now 7), Aurora (testing and major bugfixes, now 8) and Nightly (new feature work, now 9). When it comes time to do a new release, Current gets booted out, Beta and Aurora get promoted, and Nightly coughs up a build that becomes the new Aurora. It would actually be a pretty good system, except for the part where they forgot about maintenance releases and long-term support.
From the big Bugzilla thread about version numbers earlier this week:
Effective expiration, lack of bugfixes, and rapidly replaced by newer versions with bugfixes? By any practical definition, there is no stable version. They're all betas from here onwards. The whole notion of a release isn't that it's bug-free, but that it's supported for a reasonably-long period of time.
Pining for the days when The Glorious MEEPT!!! graced SlapDash with his wisdom.
You could use the super-secret Mozilla Add-on SDK
QUOTE: help ensure your add-on continues to work as new versions of Firefox are released.
Nobody seems to be mentioning this solution. Not even Mozilla.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
Really, why should I care about FF any more? They're killing us and themselves with all of these major version releases. As many others have pointed out, it's painful when dealing with web development, plugin usage, or even just to know what version is "latest". And that doesn't count all the pain with the major bugs that just languish while the UI is endlessly tweaked for no good reason (exactly why was the status bar removed?).
I'm sorry FF, but I'm sticking to the 3.6 series. As soon as that doesn't work anymore because of 1 OS upgrade too many, I'll stop using FF. If you can get things fixed and find sanity again before then, I'll stay. Otherwise, it's been a good 8 years we've had together.
What do you use instead? That's been my big problem - the plugin libraries of other browsers are no where near as extensive and a lot of the functionality I use daily just isn't there.
Plugins used daily:
- Snap Links Plus ---- a few upgrades and this should replace traditional highlighting in a browser
- QuickDrag ---- removes the need to do ctrl+click to open in a new tab
- Adblock Plus ---- simply hiding ads isn't enough for ABP, it must stop them from downloading to preserve the precious 20gb of data transfer/month I have
- Element Hiding Helper ---- for those few pesky ads you can't block from downloading
- Modify Headers ---- this one is gold
- FireFTP
- Canadian English Dictionary
- IE Tab Plus ---- for those pesky active x controls (not used daily but useful)
- Morning Coffee ---- how else would I open all my favourite sites at once? certainly not with the "dialpad" or whatever that monstrosity is called
- Chatzilla
- about a dozen different web development tools from Firebug to Live HTTP headers to MeasureIt... just too many to mension
There's just no option that does all that... at best I might be able to do it across 4-5 different programs if I dropped some of them. Slowly though they are no longer supporting 3.6 and I won't upgrade due to the numerous issues from their release model to their UI and so on... eventually I'll have switch to another browser because neither 3.6 nor 7+ will be worth using.
It was good while it lasted.
You could use the super-secret Mozilla Add-on SDK
QUOTE: help ensure your add-on continues to work as new versions of Firefox are released.
Nobody seems to be mentioning this solution. Not even Mozilla.
At least in part because having Firefox auto-update the xpi to mark it compatible for a new version breaks when modules are signed.
So for those, the developer has to release a new package. And if your release cycle is 6 months (fairly common), and Firefox' release cycle is 6 weeks, there is going to be Problems.
Both users and developers aren't going to put up with it, and will leave. Which is exactly what we see happening now - it wasn't rocket science to predict this outcome.
I think that's the idea, to stop developers from relying on version # and start coding to standards.