I love some of the innovations it brings – isolating memory and performance on a per-tab basis – it makes web surfing quicker and application development easier. It takes a lot of what’s good from the different browsers and it really will help advance web browsers in general (in the competition fosters innovation kind of way).

On the other hand, I’m not a huge fan of a few things it does. The biggest issue I have is with their JavaScript engine – they decided to go custom and we’re seeing some problems with our code at Zenbe. Not very big issues, but in my mind, if it works in craptastic IE7, it should work in Chrome. I don’t think they needed to go custom with their JS engine – I see no real reason or advantage to it, and it’s not something I really enjoy dealing with.

The other thing that I just absolutely despise, even though it’s totally minor, is the fact that they use webkit for CSS, but on text anti-aliasing they decided to go “Windows native” instead of using webkit’s text rendering methods. This results in completely unaliased text, which looks akin to IE6 (even IE7 is smart enough to anti-alias text). This just frustrates me because we’re supposed to be moving forward, not backward, and text can very easily look completely gross in Chrome and fine in everything else. So, minor, but a major pet peeve, especially since I can’t imagine why they would make consciously that choice (they said so at Ajax Experience).

So overall, while I think Chrome is going to be good for the web in general, if it came out for Mac today I would be in no rush to get it or use it. And I don’t think that will change.