ars technica:
Safari 3.1 on Windows: a true competitor arrives (seriously). “Firefox’s notorious problems with memory “leaks” are to blame, so Safari ends up using 25 to 50 percent less memory, keeping it from getting sluggish and unstable.”
Which, by the by, I overheard the funniest conversation the other day. I once had an argument with an elderly family member, who knew for a fact that Bayer, Bufferin and Anacin were all different pain relievers. [If you don’t know, all are aspirin with different or no stomach buffers]. A couple of older laptop-bearing folk were in one of our internet cafes, arguing over whether Firefox accessed “the Internets’ because it wasn’t titled “Internet Firefox”, as “Internet Explorer” was. Apparently Firefox can only access a subset of the internet? Who knew? I suppose Safari means one dons Tilley Endurables and beats through the brush of the Internet outback.
Comments:
I tend to use different browsers for different tasks, so I can wait for the next version of Firefox. Glad to hear it’s better, though. All that RAM-hogging takes away from Photoshop ... and everyone knows how much that drives me crazy ...
Font rendering on Safari is horrible, BTW. OK for testing layouts, but I don’t think you’ll be tempted to switch to it as your main browser.
I’m looking forward to FF3’s improved memory management.
Commenting is not available in this weblog entry.
Do give Firefox 3 (beta 4 is out) a try. I’ve been using it for a while now and I don’t see the same leakage as with version 2. Sure, lots (most) of the v2 add-ons are not yet ported, but this is changing quickly.