|Chrome not so shiny on OS X
||[Sep. 3rd, 2008|11:36 am]
I got to play around with Chrome last night on my Windows machine, and all I have to say is as soon as they get the OS X port done, I'll be spurning Firefox, which, though an improvement over IE and Safari in some respects, is kind of bloated these days. It also tends to lock up and go wonky on OS X in ways it does not on Windows.|
It surprises me that A) They develop on Windows and then port and B) They didn't build and test on OS X and Linux from the beginning of the process.
Point B especially is kind of a dumb move -- you know you're going to support all 3 OS, why aren't you designing to that goal from day one? Given the amount of work that has been done on platform-independent UI programming, and the number of engineers Google could throw at the problem, it's inexcusable.
Given Google's interest in mining data within GMail & other applications, I wonder what kind of info their browser will be sending back. Until I see some substantive analysis of that, I'll stick with Firefox.
2008-09-03 05:07 pm (UTC)
I wouldn't assume it's a "build Win then port" deal. I think it's a "We're putting IE in our headlights" deal, such that they focused on getting the Win version out into the marketplace first. The overall look and feel of Chrome is very platform-neutral, in that it doesn't seem to be using any windows built-in stuff for widgets and such, so it seems likely to me they've got a far-along OSX version, it just wasn't as important to get that shipped as quickly.
If I had to guess, the windows version took priority so the Chrome 1.0 release times with the release of the first android phone. I bet there that will be an advantage to using chrome in conjunction with your android smartphone, and the will market it as the windows users version of the iphone.
yeah I was interested in this announcement because firefox is so awful on osx. I finally had to revert to ff2 so it would be usable.
chrome on xp sucks at flash + streaming