PanaGeek

I used to be a die-hard Camino fan (starting back in the Chimera days). A few weeks ago I started using Safari. The reason is that I can copy snippets with text and images from Safari into Mori, where Camino only lets copies the text. Anyway, I decided to do an empirical test, to see how the browsers use resources. I’ve done this in the past, and Camino usually won. Now, Safari is getting the better of Camino in both CPU and RAM usage. I opened six identical web sites on both browsers and here’s what I’m getting:

Browser | CPU | RAM Camino 46.6% 72.4M Safari 25.6% 49.6M

and Camino is not responding, according to Activity Monitor. It makes me a little sad, considering that I’ve been a Camino fan for so long. Oh well, the browser of the day is Safari.

Well, I committed my Documents folder to a Subversion repository on my network storage device and dutifully checked it out onto my laptop again yesterday. Today, when I went to sync Quicken, I found that I couldn’t open the data file. This web site thankfully had the answer. Quicken uses resource forks on OS X (resource forks were a big thing pre-OS X, I didn’t think anything still used them). After running through the commands as shown on the site, I was more-or-less happily broke to the last penny again. While this wasn’t meant to be a subversion bashing, it reinforces my desire to move to a DVCS – specifically Bazaar. More on that in the future.