Yeah, and Chrome is ... well, it's a reasonable 80% solution for an alpha product from what people keep saying, but I still can't actually try the damn thing on my usual machine.
Because, once again, a bunch of software developers have forgotten to obey the %*&(ing theme. Chrome's URL bar successfully takes my foreground colours and completely ignores the background colour setting - so I get a white hostname and a light green path on a white background.
And Firefox 3's awesomebar and the way it handles self-signed SSL certs both make me incredibly happy - maybe chrome does these just as well, as I say I can't tell yet (FVO "can't" meaning "choose not to fill the prerequisites in order to be able to", of course :).
But it strikes me that there are probably a lot of issues like the one I'm complaining about that don't matter to most people but are a showstopper for -somebody- - and firefox has probably nailed almost all of those by now, either in core or in an addon.
Seems to me that the key point of chrome is to provide a decent amount of testing for the tech that's going to go into site-specific browsers for various google applications - really, truly going head to head with firefox doesn't really seem to me to achieve anything for google when -somebody- crushing IE is likely more important to them than specifically them doing it and firefox already has a head start.
Because, once again, a bunch of software developers have forgotten to obey the %*&(ing theme. Chrome's URL bar successfully takes my foreground colours and completely ignores the background colour setting - so I get a white hostname and a light green path on a white background.
And Firefox 3's awesomebar and the way it handles self-signed SSL certs both make me incredibly happy - maybe chrome does these just as well, as I say I can't tell yet (FVO "can't" meaning "choose not to fill the prerequisites in order to be able to", of course :).
But it strikes me that there are probably a lot of issues like the one I'm complaining about that don't matter to most people but are a showstopper for -somebody- - and firefox has probably nailed almost all of those by now, either in core or in an addon.
Seems to me that the key point of chrome is to provide a decent amount of testing for the tech that's going to go into site-specific browsers for various google applications - really, truly going head to head with firefox doesn't really seem to me to achieve anything for google when -somebody- crushing IE is likely more important to them than specifically them doing it and firefox already has a head start.