Yeah, I’ve found that when I’m using FF, it’s good to start it up, do what I gotta do, and then shut it down. Safari on the other hand, I often leave running for weeks on end before it starts to suck all the spare cycles out of my CPU.

I haven’t actually tried FireGPG, so it might not be a great implementation. I presume that Google will open source the Safari Gears bundle, and FireGPG already proves that it’s technically feasible to brute force signature/encryption glue into a GMail message. All the hard work has been done, it’s just a Simple Matter Of Programming (TM) to take the eventual Safari Gears bundle sources, and hack in a FireGPG-a-like GPG callout :-D Not to mention a great way to gain hacker kudos for the person who actually does it…

With regard to FireFox, 9 times out of 10 it seems to run noticeably slower on my macbook – something is very wrong when in 2007 you can’t even scroll a webpage without it lagging and using up questionable amounts of memory. Though of course for web development, it beats everything else to a pulp – so i guess its an acceptable compromise.

Personally i just use Camino for normal browsing, which nicely integrates with the Mac OS X keychain, plus its not as slow. The only problem is, it doesn’t really support extensions, let alone FireGPG :( Although… perhaps some applescript hacking could help to provide the equivalent functionality.