Safari (part 2)

Safari on Windows is still terrible, even after the last few patches, but I didn’t start an entry just to bitch a little. After Safari:Windows was released, a lot of people were bitching about the fact that it’s font’s looked blurry, while I hadn’t noticed that at all. It turns out that Windows and Apple approached font handling radically different. This blog entry tells exactly what and where (and why).

As someone who had done a bit of DTP himself, I tend to prefer the mac way of font handling. I want things to look the way the creator had intended it (within limits). To help things, my eyes have grown used to the mac way of font smoothing, so I actually didn’t see the problem until it was pointed out to me.

One more thing on browsers: lately I was multi-browsering on my iBook, because Safari used native widgets that were easier on the eye, and I needed Firefox for sites that Safari couldn’t handle. Opera just isn’t an option for me, I don’t like it’s interface, too many bells and whistles, and still not native. But, at last, I have found the browser I was looking for: Camino. There are still a few things that bug me, but it is the best browser for mac I have seen yet. It Just Works™

New (and barely stable)

In a perhaps daring and awe-inspiring, or foolish move, Apple has decided to leverage it’s iPod advantage in the desktop computing market. Last monday apple announced that they are bringing Safari to windows. For now it is a separate beta download, but I’m pretty sure that once it is finalized, it will be bundled with iTunes, just as Quicktime already is. A technology geek like me has to try new stuff, so I have tried Safari Beta for windows. The first site I tried (that rendered badly in Safari under OSX), crashed Safari for Windows. Let’s leave it at the observation that there’s a lot of room for improvement.