Google Chrome is a quick, quick browser, but if you have it set to automatically detect your proxy settings, it can be IE6-slow to launch. Here’s how you fix it:
Brilliant. Simply brilliant. Google has released a plugin for IE6+ that will run Chrome inside a frame, thereby allowing users to experience a modern browser and developers to quit coding for a woefully-nonextinct dinosaur.
Wow. This guy wrote a NES emulator in, get this, Javascript. Yes, Javascript. You’re going to want to give this a try using Chrome, though…the JS engines in other browsers will only give you about 5 frames per second (compared to 50+ using Chrome!).
Firefox was the kick in the pants that Microsoft needed to finally improve IE6. It looks like Chrome will (hopefully) have the same effect on Firefox. Isn’t competition great?
Next year, Google will be releasing the Chrome OS. Chrome OS will be a quick-booting, minimalistic platform that will support running web applications (think Google Apps, etc.) on Chrome. It will initially be released on netbooks.
The cool part? It runs on a Linux kernel. This will be great for Linux marketshare (although most folks will probably have no idea that they’re not using Windows anymore). :)
People only use IE because it’s the browser that comes with their PC and they don’t know any different. I can count on my fingers the number of fools I’ve seen that actually use it on purpose.
Yet another Chrome post…but hey, some of these are really cool. If you’re only going to try one, go with about:internets (much cooler if you’re on XP).
Chrome is very, very promising. I’ve been using it for Gmail, Google Reader, and Remember the Milk for the last few days, and it screams through the copious amounts of Javascript they require.
When they release a full-featured version, I will definitely think about switching. If they can get a nice library of plugins together Firefox will have a legitimate competitor on their hands.
I have only one complaint: for some reason, after a few minutes my hard drive starts thrashing, and I have no reason why. Killing the program seems to fix it. Hopefully there’s a fix or explanation for this behavior soon.
