Google Chrome - What's the Deal?
Now, I admit bias against this browser, mostly because my mac-loving ways don't allow me to easily use it just yet. I don't know Chrome well enough to judge it. So, I will be kind. However, I can't help but wonder why so many are so excited/afraid/enamored with this new webkit-based browser. Can it be that compelling or that evil?
Well, I will have to install it on my *sigh* server, and see what is the big deal. For now, I will take words from what I have read so far. Chrome is a container of the best sort; there's no cross-contamination between your sub-containers. So, the strategy is to make each tab a separately-handled entity, which can crash and burn on it's own. Neat. The UI is minimal. Whether or not that's good (think of the changes from IE6 to IE7 for most users) depends on how well everything else works. Personally, the less there is, the better it might be, since there is less to remember, but more to adjust to. Since we have webkit, the html rendering is fast. With the V8(http://code.google.com/p/v8/) runtime, the javascript is likely fast as well. So, it's speedy, from various reports. So, it would render as well as webkit browsers will, have very fast javascript, and separate all your windows from breaking each other (lol, flash). Sounds good to me. But, still... we will see if this was actually needed. I suspect Chrome will be around for the long haul.
More Reading:
