
Google hasn't officially announced it yet, to the best of my knowledge, but it looks like they're very far along with the development of a new Web Browser based on the Webkit rendering engine. They call it Google Chrome.
The interesting part isn't the rendering though. The underlying architecture is what makes this very exciting news. As everyone nerd knows, websites and web applications are becoming more and more reliant on Javascript to get things done. Most bottlenecks in modern web browsers seem to come from Javascript-intensive sites choking up.
As such, Google has been hard at work on their own Javascript virtual machine for Chrome (and anyone else who wants it) called V8. I don't understand all of it, but the part that seems interesting to me is that all code is instantly interpreted into machine code, allowing it to fly at about one million miles per hour. There's also neat bits about the ease of finding pointers and garbage collection that are going to make V8 the next generation Javascript engine.
The other killer feature, which is the bane of all modern browsers to incorporate tabbed browsing, is individual processes per tab. Say you load up twenty tabs in Firefox right now and one of those tabs loads a site that goes apeshit. In today's browser-worldTM you would most likely either have to restart Firefox entirely, or Firefox would just crash. Chrome aims to fix that by putting all tabs into their own processes, so if one tab freaks out, you simply close it and the process is gone. Everything goes back to normal.
All of this (unconfirmed) information is coming from a thirty-eight page comic that was shipped to Philipp Lenssen. I see this as huge for Google, and huge for end users. Faster web apps for us, amazing open source software for developers, and the world being one step closer to using the Internet as an OS for Google.
There's been a lot of talk about a Google OS for a long time, and I think this might be it.
Update: Looks like it'll be out tomorrow (September 2nd) for Windows.
••

