Google Chrome: Stability is a win, but where is Python?
·——
····
··
—
·····
···——
——···
With its
new web browser, Google aims to deliver simplicity, stability, and speed. The UI
is nice and simple, but only marginally so over my usual Firefox setup. And the speed of the new JavaScript engine won't matter until people can build sites for it, and you've got the lowest common denominator problem there. Stability is the biggest immediate win. Yes, there are bugs:
Now, if IE or Firefox present such a dialog, I know with the certainty of long habituation that clicking "OK" means saying good-bye to all of my open tabs. I usually observe a moment of silence before proceeding. It helps the healing process.But guess what happens when I click "OK" on the above dialog? Nothing. The dead tab is already closed, and Chrome doesn't skip a beat. I keep on browsing. Applying my applications. No mourning, no grief. Blip ... barely. That is nice.
You know what it took to turn "OK, please kill my productivity" into "OK, please stop interrupting me"? It took an entire bottom-up rewrite. That's a lot of work to make my life a little bit easier. I'm glad Google did that.
Now, I would be really paranoid about privacy if it weren't
open source, and I'm still tempted to compile it myself (tip: delete
rzl.dll). But I'll be
reallyhappy when they add a Python virtual machine. Their
server-side offering is Python-based. Firefox has toyed with the idea (right?), and Microsoft has
an implementation. Hey, it could happen.
·——
····
··
—
·····
···——
——···
Feed back to
Chad Whitacre.