tewha.net

With a surprising lack of anger, The Angry Drunk absolutely nails the good and bad of Google Chrome.

Since it’s as much a proof of concept experiment as a real browser, the overly simplistic interface isn’t a surprise, but it’s still gone too far and become inconvenient to use. And like our drunk or soon-to-be-drunk friend, I found the tab names condescending — though unlike him, to me it was a subliminal thing that irritated me without me being able to explain why or even that it was the tabs doing it. So I’m grateful he was able to put into words what I didn’t like about the options screen.

I’m very curious where this will go when Google ports this to a system where hiding the menu bar isn’t really an option.¹ Implementing the right subset of standard browser commands in the menu bar is going to be critical.

1. Hiding the menu bar is, of course, an option on Mac OS X, but it only makes sense with full screen applications. [↩]

After my last post, Firefox fans are probably wondering why I’d bother. The truth is that even with the annoying bugs present in it, I still find Safari the least offensive browser, given Firefox’s window focus drawing bug, inability to be dragged from the status bar, the botched spellchecker integration, slow launches, etc, etc.

I’m sure most of these will be fixed, but Firefox is a well of platform integration problems. The well does have a bottom, but we’re probably not near it yet.

Safari 3.1 still eats cookies, although it seems to do so much less often than 3.0. I just hit it for the first time since updating.

So what do you do when your cookies all disappear? Well, you can actually use Time Machine to restore them. The cookies are stored in ~/Library/Cookies in a single file called Cookies.plist. Trash this file, then use Time Machine to restore one from a couple hours previous.