Chrome has been making some major inroads into the browser market share of both Internet Explorer and Firefox. It is now close to tied with Firefox and the trend seems to favor Chrome. This is no doubt due to Google leveraging its marketing power to push Chrome. The new Chromebooks will certainly help push the name recognition further.

I use both browsers regularly (8+ hours a day, side-by-side on dual monitors) and after a couple years I still find myself using Firefox first. I figured I would try and compile a mostly-objective list of the reasons why I prefer Firefox. This comparison is done for Chrome version 16 and Firefox version 9.

Continue reading...

Google Chrome's Omnibox knows what you're looking for. If you type in a regular-looking web address, such as google.com, it knows to take you to that website. If you just type in pizza, it knows that you want to search for pizza and will take you to search results.

But what if you have a term, such as pizza, defined as a host that points to a virtual host in your web development environment? Instead of taking you to the corresponding site, Chrome still takes you to the search results, along with a little pop-down box that looks something like:


Sure, if you had just typed http://pizza/ in the first place, Chrome would treat it as an address. But why should you have to do that? If the host exists in the hosts file, Chrome's default behavior should be to treat it as an address and not a search query.

Continue reading...