Hey tech-savvy LJ brain

[beetiger]

I know a few reasons why I don't need Firefox3 (not compatible with some stuff I use, perfectly happy with the current setup, etc.). Are there some good reasons why I *do* need it?

Comments

[bkdelong.livejournal.com]

Not that I can tell as of yet. I am very bummed that they removed support for Google Browser Sync. They better get their act together with Weave. I'd wait for the next release or for your extensions to catch up.

[barberio.livejournal.com]

It's not so much 'removed' as they made large changes to how it stores bookmarks, and Google haven't made any effort to update their extension to work with it.

[barberio.livejournal.com]

You might be interested in http://www.webmynd.com/html/

[varjohaltia.livejournal.com]

I did give it a short whirl yesterday. It's a lot faster, and I'm hoping it leaks less memory. That being said, I'm not going to switch for my daily use until there's something to replace Google Browser Sync, because I rely on that a lot too.

[orb2069.livejournal.com]

How about Foxmarks? It offers a lot more control than GBS.

[varjohaltia.livejournal.com]

Alas, it only syncs bookmarks, not passwords, history or cookies. Bookmarks are the easy part, passwords and cookies are the harder one, and the one I specifically rely on. Google did it in a way that I found acceptable, where I enter an encryption key and they only ever store encrypted content for me, so Google doesn't have access to it.

Rumor has it that Weave will do this eventually, but so far it looks quite sketchy.

[otter3.livejournal.com]

A little faster, and tag-based bookmarking.

[pathia.livejournal.com]

2.x always had some sort of memory leak, if I ever left it open for a few hours it would somehow manage to swell to nearly 2GB and eventually explode my system. 3.X even the betas, have never done that.

[fire-of-gold.livejournal.com]

That's the primary reason I upgraded. Though fiddling with the beta/RCs also showed me how much snappier it is. On he other hand, if you don't have a dozen extensions or so, you might not have as many difficulties as I did with 2.x. What can I say, I'm a tweaker :)

[shatterstripes.livejournal.com]

Because you need the experience of starting it up, letting it update your extensions, and then getting the crash reporter. Twice in a row.

I now have two crash reporter windows sitting on my machine, trying to submit their data. Woo! I sure am glad the other browser on my system isn't IE.

[revar.livejournal.com]

I suspect that plugin extensions need to catch up with browser, and are what tends to crash things right now. I don't use many, other than the web developer one, so FF3 has been very stable for me.

And so very much smoother scrolling and cleaner rendering. Especially regarding border-radius CSS.

[postrodent.livejournal.com]

I'm using 3 myself and it's very nice; the installation was real crisp and everything from the previous install made it across intact. But it's an incremental improvement, nothing like the transition from, say, IE to firefox. If what you've got works, stay with that.

[lediva.livejournal.com]

Yeah, if you're not having problems, don't bother.

I got bit regularly with the memory leak bug, so upgrading has been a net win for me.

[stellans.livejournal.com]

I had a lot of browser crashes with FF2, so I was happy to see the update. That said, if I'd realized so many of my extensions/tweaks weren't going to work I might have waited on updating. But I'm liking that it hasn't crashed yet, and Version 2 crashed every other day or so. Probably because of all my extensions, LOL!

[cattitude.livejournal.com]

No.

Eventually, when they stop issuing security patches for FireFox 2 (a few years, most likely), this answer will change.