Hope all is well!

Thanks!

N.

This article in the NY Times compares the convention rhetoric with the truth and is worth exploring.

And this BBB page has a spreadsheet on the candidates and the issues that I think is helpful.

That doesn’t mean that Camino leaks and doesn’t release memory to the same degree as FF2. In any case, I certainly will be looking forward to updates to Camino that add in FF3 features such as the new Gecko engine and better memory management.

However, for the time being, in a comparison on the Mac between Camino 1.6, Safari 3.1, and Firefox 3 Beta 5, I prefer Camino.

Firefox 2 leaks memory badly and doesn’t release memory, even if you run it with zero add-ons/extensions installed. This is well documented, you can search on the Internet many articles and screenshots showing Fx2 using up to 1GB of RAM or even more because of the memory leaks after a few hours. With Firefox 3, this is non issue now.

http://blog.pavlov.net/2008/03/11/firefox-3-memory-usage/

As far a page rendering speed, I don’t notice any appreciable differences between FF2, FF3, Safari, or Camino. This may be different if you connect via a slower connection, but on the fat pipes I use at both work and, to a lesser extent, at home there is not a noticeable difference.

Your final point about memory usage is more of a dicey one. First of all, FF2 was a memory hog on all platforms. However, the memory issue was made more complex because many of the problems were attributed to sloppy code in the add-ons and plug-ins in Firefox. FF3 claims to fix many of the memory issues in its predecessor (and certainly it makes great strides in this area) but it remains to be seen if add-on and plug-in support drags this area of performance down again. On the other hand, I haven’t had too many problems with Camino being a hog in the long time that I’ve been using it. It certainly never feels slow and unresponsive as you claim.

Long term memory management, though still important in browsers, is less of an issue in the current generation of browsers in any case because they all have session support. So, if you notice slow performance after a few days, simply quit your browser and relaunch it. The program will remember all the tabs and windows you had open so, as long as you weren’t in the middle of filling out a form, you’ll be back right where you left off with a lower memory footprint. For me at least, this eliminates many of the memory usage concerns with any browser.

Camino 1.6 still uses the same old Gecko 1.8 engine as Firefox 2, so all the problems and slow, unresponsive feel is there, even if it’s a natively built Cocoa app.

http://www.seriouseats.com/talk/2007/11/cup-pies-the-new-revolution.html

You gotta love the Kronos they are so incredibly eclectic!