Slashdot Mirror
Firefox 1.1 Scrapped
An Anonymous Reader writes: "The Firefox team has decided to scrap the planned 1.1 release (already in Alpha 2) and instead release the final version as 1.5 due to the significant number of bug fixes and changes. The 1.5 feature complete beta is expected next month." From the article: "We are planning for a Firefox 2.0 and 3.0, but will divide the planned work over (at this point) three major Milestones, 1.5 (September 2005), 2.0 (unscheduled) and 3.0 (unscheduled). All major development work will be done on the Mozilla trunk, and these releases will coincide with Gecko version revs."
There isnt any logic behind version numbers, that's why they're making news out of stuff like this.
As far as i'm concerned, I don't really care about what version number my browser is, as long as it's the latest, and it doesn't start with IE.
Interesting to see that FF has to play catcup on the version number game.
Are people really that silly to think that the (soon to be released) IE7.0 is almost 6 versions "ahead" of FF?
I guess this is a sacrifice we need to make to get some of the mum&dad market.
Sparks:Gadget:Beer Maker
Not that I use it, but I feel I must point out that IE is free. Isnt that kind of why opera gets crushed? It's a commercial software package squashed between an awesome free package that you need to download, and a sub-par package that likely comes with your computer. P.S. I dont use opera either.
...they stopped new development on Firefox altogether and got Thunderbird a little more stable. Oh.....and they need to get that lightning calendar integration working, too. Then I could actually think about moving my organization over...
This space intentionally left blank.
The timing of this seems very unfortunate. With 1.1, we were likely only a month or so away from having real, native SVG support in a major browser - and likely *before* IE7 was released. That might have given SVG a chance to be noticed for real by the public in a way that hasn't happened yet; maybe even enough to put pressure on the IE team to actually implement it themselves.
With the new delays, there's every chance that the IE7 betas will be out before SVG has a chance to become noticed by the general public. That just seems... unfortunate.
Does slashdot suddenly have something against Mozilla / Firefox? This reminds me of the "Mozilla suite discontinued" and the "Thunderbird (some version) canceled" stories. These could EASILY be re-worded to put a more positive spin on it.
How about: Firefox leaps ahead to 1.5!
Going on to describe: The vast number of improvements to Firefox has warranted a larger version increase, skipping over 1.1 the next release will be 1.5...
Similarly the previous stories could have been "Mozilla.org focuses exclusively on Firefox" and "Thunderbird flies ahead to version (number)".
Of course it didn't help the previous two were copied out of context from Mozillazine articles. Hmm... I don't see anything about this at all on Mozillazine yet.
Anyway Slashdot should be trying to help Mozilla.org and Firefox, not trying to sensationalize every change.
Having worked in a corporate infrastrucuture for far too long, I have to sadly say, that the biggest enterprise drawback to the use of FireFox is the lack of a Admin kit, that would allow you to customize which extensions you push out with Firefox.
It would also be nice to have an MSI based installer for easy deployments via exisiting application deployment engines (AD, SMS, Zenworks, etc) and the ability to customize the broser via Group Policy.
I know all of these only apply to the Windows world, but I think these kind of things would help Firefox in the long run.
Well, no, it's not a better option. For those who don't need the feature, it makes the browser bloated.
What they need is to include these crucial extensions in the installer as optional packages. The firefox installer should come with a laundry-list of important extensions nicely bundled together and thoroughly documented so that a user can either a) just get the minimum or b) make it a point to grab the tools they need. It keeps the core browser light, but it means that people with specific (but common) wants/needs don't need to go hunting around the extension page.
Simple packs like "Usability", "Internet Explorer Familiarity", "Web Developer", "Power User", "Multinational", etc. that bundle together commonly used relevant extensions would go a long way.
AFAIK,
the real reason for the Winamp 2, 3, 5 version numbers is because 5 = 2 + 3.
Everybody loved v2 and when v3 came along, it hogged memory, crashed everywhere and generally ran like a dog. They then went out and built the capabilities of 3 into the code base of 2 hence the 2+3=5.
That said, it's still not a very good numbering system - but at least there is some logic to it.
So instead of being patient with the available plugins and enjoying the other features of FireFox, you're going to move to another browser that doesn't have these plugins to begin with and therefore will never be 'fixed', since they don't exist?
Unfortunately I'm having trouble with your logic here.
[DISCLAIMER: This post is a work of satire and should not be misconstrued as a holy text upon which to base a religion.]