The new Google Chrome browser: a bad day for Firefox

The Firefox angle is what puzzles me about Google’s announcement that it is is launching a new open source browser. We should get to try it tomorrow; perhaps we’ll see that Google is successfully reinventing the browser. In particular, this is a part of what is sometimes dubbed the Google OS: the client for cloud applications running on Google’s servers:

Under the hood, we were able to build the foundation of a browser that runs today’s complex web applications much better.

Google is using some proven technology in the form of the Webkit rendering component (as used in Apple’s Safari). I imagine it can do a decent job. But why? From Google’s perspective, the browser market was shaping up nicely already. Microsoft’s IE has a still large but declining market share; Mozilla Firefox is growing, has a vibrant community, and relies on Google for the bulk of its income in return for making it  the default search engine – a deal which has just been extended for three years.

Now Google appears to be going head-to-head against Firefox. It won’t necessarily succeed; Firefox has lots of momentum and will be hard to shift. Equally, I doubt that Microsoft’s market share will decline significantly faster against a Google browser than it would anyway against Firefox.

The risk is that this will split the open source community.

As for Firefox, this can only be bad news. It has the embarrassment of relying on a major competitor for its income, and the knowledge that it is driving traffic to a company that will push users to switch to an alternative.

Maybe Google Chrome is so good that it will all make sense when we get to try it. For sure, it is an intriguing development for web applications and I’m looking forward to seeing how well Google can substantiate its claims that it is “much better” for the job of running them.

Don’t tell me to turn off Vista’s UAC

I’ve been looking at music servers and music ripping software, and came across Ripfactory Micro, a fast and easy to use solution.

Unfortunately when I ran it on Vista it came up with this message:

Then it exits. I looked at the support pages and found that this is a documented problem:

If you are trying to run our software on Vista and get an "Unable to enable autorun" message, you have to turn off the User Account Control (UAC) as the program requires access to a registry key to determine autoinsert status.

It’s true. I checked using Systernals Process Monitor. The app asks for access to HKLM\System\CurrentControlSet\Services\cdrom\autorun. If it finds it disabled, it throws up this dialog:

This is such nonsense.

First, if the app finds autorun enabled it doesn’t need write access; and read access comes by default, so why break the app on Vista for this?

Second, there is no need to disable User Account Control to run the app. You can either set it to run as administrator (right-click the shortcut, compatibility tab); or else grant the current user read-write access to that specific registry key – not ideal, but either of these would be better than disabling UAC.

Third, a support note like this should at least hint at the implications of disabling Vista’s primary security feature.

Otherwise the app seems to work well, faster then iTunes, and downloads cover art. I still prefer dbPowerAmp though, because it links to AccurateRip to check the integrity of your rip.

Technorati tags: , , ,