Slashdot Mirror
Mozilla Firefox 2 Alpha 1 Available
Mini-Geek writes "Code-named Bon Echo, the first Alpha of Firefox 2.0 is now officially available. You can download it at ftp.mozilla.org. From the article: 'Here are some new features in Bon Echo Alpha 1 that require feedback: Changes to tabbed browsing behavior, New data storage layer for bookmarks and history (using SQLlite), Extended search plugin format, Updates to the extension system to provide enhanced security and to allow for easier localization of extensions, Support for SVG text using svg:textPath'"
We all know that Firefox has had (and still has) a lot of memory issues. Will embedding a database in memory help or worsen these issues?
I haven't used SQLite, can anyone with experience using it please comment?
I've always wondered why bookmarks don't sort themselves by most often used to least recently. Maybe it will happen now. But the changes to tabbed browsing behaviour - hmm - I hope that means something like memory optimisation and not making it more like the tabs in Konqueror. Blech.
Get your own free personal location tracker
Is there a plan to add XForms support to Firefox, or will they be waiting for XHTML 2.0?
I've been toying around with the new alpha, and it has some interesting additions. But heck, the changes made do not warrant a jump in major version numbering in my books. But I guess that's because I'm used to how version numbers are in the Free Software world, where a jump in a major version number usually means there was a rewrite, or ABI was broken in favour of some fundamental changes.
I'm definitely not seeing that here with Bon Echo.
Not that this is a bad thing -- heck, I'm as much against featuritis as the next guy. But frankly I see less change here than from 1.0 to the Deer Park alphas.
IMHO the #1 thing the guys should have focused on for the 2.0 release was to make Firefox a XULRunner application.
I find it very strange that the winners of the recently posted FF Extensions contest do not work. The extensions that is. I like this alpha of FF 2 but I wish I still have the extensions / Themes I had before still working.
-- Josh
"Whoopie! Man, that may have been a small one for Neil, but that's a long one for me!" - Pete Conrad
I mean, Mozilla used to be slow and steady, now they are firing out updates on .5 increments.
.1 version increments. If they are just trying to drive up the version number to match I.E.'s 7.0, then they will find that Firefox performs about as well as I.E. 7.0, or even less so considering it took Microsoft 10 years to get there.
Is this good or bad? I think Firefox will end up becoming bloated and bug ridden just like IE if they keep up this kind of product update cycle. Firefox 1.5 hasn't even been out for 6 months and they are previewing version 2.0.
While I do think that some open source projects move a long at a pace that make snails impatient, I have found that this quick turnaround for FireFox versions isn't beneficial in the long run. I have found there to be more problems in each new version, and I have stopped using Thunderbird for several problems that haven't been addressed yet (such as opening up the wrong email when you click on a header).
I think Mozilla should slow down a bit, or at least go back to the
I haven't thought of anything clever to put here, but then again most of you haven't either.
I'm not all that enthusiastic about yet another iteration of Firefox... It's my primary browser and I do like it, but it will never be the browser that I would regard as the ultimate.
I envision a web browser which is the browser equivalent of Linux; a collection of simple programs performing very specific and narrowly defined tasks, all working through clean APIs or protocols. The HTML rendering being split off entirely, the javascript in its own library, image rendering separate, cookie management, security features, history management, bookmarks display, etc. Ideally, the various parts would be so simple that the barriers to development would be lowered drastically resulting in the organic rise of alternatives in the various segments; imagine having a flamewar over which js rendering plugin/library were better!
Extensions are not the solution by far. The functionality decentralization necessary to realize the vision of a browser like this far exceeds what the design idea behind extensions was.
Firefox will never be this. The only thing I've seen which might be salvaged into some sort of semblance of this vision is Kazehakaze, though that remains to be seen (I'm not sure you can even hotswap html rendering in Kazhakaze; I've never managed to keep it from crashing for long enough to test).
Blearf. Blearf, I say.
New features planned for Firefox 2.
What a fool believes, he sees, no wise man has the power to reason away.
Most web people I know design for Firefox and then check IE for any weirdness. That seems to be much better than the reverse. The only exception would probably be certain CSS tags that IE has yet to support.
then email google and tell them their calculator thingy doesnt work.
only someone else who owns a delorean may criticise my signature. :p
(1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
I am delighted to see this. Some of the mozilla stuff still uses Mork, which is truly and utterly horrid. I recommend reading this delightful code by Jamie Zawinski, which has a brilliant rant about it: