Blogs, Internet, Web 2.0, Tags, CSS, XHTML, Mac, Everything ©

Okay, here we go. To tell you the truth, I didn’t think it would actually happen. I always thought that the rumours about Google’s browser are just wishful thinking - and look, it finally happened.

Google is making its own browser.

Let me repeat that, in a case some of you are not aware how big is this.

Google is making its own browser.

Sure, the rendering engine is based on WebKit. And this is also one of the reasons it may be the greatest browser ever.

If only…

I don’t know about you, but for the last few months (some may say a year or two) the WebKit team was doing wonders. Not only is their browser engine so portable that it can run on multiple various devices (starting with normal computers, going to specific software implementations, such as Adobe AIR, and ending on the Google Android platform).

Even if you’re using Firefox on a daily basis, most web developers in the world would tell you that WebKit (or to put it simply, Safari) has the best standards support, the best JavaScript engine implementation and is up-to-date on almost every web language out there.

But also everyone could say that their browser sucks. Ugly interface, no interesting extensions, and well… Nothing which would really make you say “This is cool, I want it now!”

Even Internet Explorer is better, with their WebSlices and Accelerators in IE8 (yes, I’m actually fond of the idea, and even though it’s already been in use through extensions in Firefox, I’m more than happy these technologies are going mainstream with full-browser support).

One thing that WebKit lacked, was a good browser.

And now, here’s Google Chrome. A browser with:

• A new user interface, where the tabs are at the most important, as they should be
• Gears integration out of the box (Hey Google, that’s one less browser to worry about. Now just make Opera and Firefox use Gears, and we’re good to do)
• An uber-fast JavaScript virtual machine, which will make working with JS-heavy webpages a breeze
• And the most important thing to me, one which Philipp didn’t give much exposure to, is the “one tab - one process” pattern

Regarding that last thing, this is where Google may have really won not only my heart, but most of the IT-aware crowd out there. How many times were you furious that some website died on you - well, along with the whole browser? How many times did you swear at a 1000-rows table, where each row has three events attached to it, making the whole work a real pain?

Google is here to fix this, and many, many other problems.

In the end, I want to emphasize the first page of Google’s Chrome comic, which really sums up my thoughts.

Yes, Google, that would be great.

And from the bottom of my heart, thank you. You’re revolutionizing the web yet again.