Tagged Safari

I’m honestly a bit puzzled right now. For some reason, as I was browsing a web page in Safari, the fan in my Macbook started to spin, and it got to the point where it must have been spinning full speed, which is quite loud. I looked at my CPU graph from iStat menus and for some reason, both my CPU’s cores were intermittently running at 100%. First, one core would go to 100%, then the other, then split it 50-50, and so on.

I looked at the process list, and apparently bzip2 was the process taking up so much CPU. What the hell? I’m not running anything that would even think about needing bzip2 to compress something — just Safari. And about 10 seconds later, the bzip2 process was gone, and the computer’s back to normal.

Googling didn’t help, so: what the hell?

I’ve had it with Firefox on Mac OS X. On Windows, it’s fine, but on Mac OS X it’s unbearable. It crashes too often, it’s slow and sluggish all the time, and it just eats up my RAM1. So I’m trying something new — I’m using a nightly build of WebKit.

I started thinking about switching when I read an article on Ajaxian that mentioned that more and more web developers were moving to Safari/WebKit for casual browsing, due to the speed and ease of use. I can’t believe it took me this long — everything is snappy, the way I would expect a modern piece of software to work, and the nightly is running great.

Inquisitor is great, too. It makes searching Google fun and easy, and as an added bonus it looks good. It just took me a while to figure out the shortcut for the search box, but once that was done it’s been smooth sailing since then.

Oh, and the font rendering in Safari is so much better. I’m never going back. Never! Oh, and WebKit is for Windows, too, now. So when I switch to Windows XP when I buy a new PC (gasp), I’ll still be fine.

  1. Put it this way: when I quit Firefox, my RAM usage goes way down. Way down.