Industry


Ads by TechWords

See your link here


The real reason Google is making Chrome

The real Labor Day storm wasn't Gustav, it was Google's announcement, by comic book no less, that it was releasing its own Web browser: Chrome.

So why is Google doing this? First, off let me tell what it's not. It's not an attempt to kill off Internet Explorer or Firefox. Google just renewed its partnership with Mozilla and that deal, which runs through 2011 accounts for 85% of Mozilla's income.

So what is it then? There are five reasons why Google is doing this, and, if you read the comic book closely - yes, I'm serious - and you know technology you can see the reasons for yourself. These, in turn, lead to what I think is Google's real goal for Chrome.

First, Google wants a browser where its applications like Gmail, Google Docs, it's just introduced Google Video will run as quickly as possible. To do this, Google is introducing a new multi-threaded JVM (JavaScript Virtual Machine), V8.

What V8 does is act as a JavaScript compiler rather as an interpreter, which is how most JVMs work. Anyone who's done a lick of programming knows what this means: compiled programs run much, sometimes as much as orders of magnitude, faster than interpreted programs.

Google also wants a browser that can run multiple applications at once. As it is, the mainstream browsers are single-threaded, single process programs. So, for example, if one JavaScript-based program is slow or hung, everything on the browser runs slowly or not at all. In Chrome each tab has not only its own thread but its own process. By using multiple threads and processes, each browser tab runs at full speed even if one tab's application freezes up.

Next, Google wants a browser that can handle large Web-based applications. To make that happen, Chrome includes better memory garbage collection for both its Web tabs and for its V8 JVM. The net result is a Web browser that takes up a bit more memory when you first run it, but doesn't have the memory leakage problems that cause other browsers to slow down the longer you run them as they slowly but surely eat up all available memory.

If you're going to be running a lot of Google applications, Google knows that you want to be sure that your work is secure. To help with that, Google is sandboxing tabs. Sandboxing is a tried and true security measure that gives an application, or in this case, a Web tab, only the permissions it needs to run. Google will be using a relatively strict permissions system, where a tab requires express permission before it can do anything with data on your system.

Finally, Google is using WebKit, the Apple/KDE-based open-source Web browser engine. WebKit is also what Google is using for its Android mobile phone system.

WebKit is best known for being small and efficient. That's one of the reasons why it's in Android, Nokia uses it in some of its mobile devices and Apple uses it in the iPhone.

Now, what do you get when you put this all together? You get Google designing not so much a traditional Web browser, but a Web application platform. And, it's not just a PC Web application platform, it's one that will work equally well, without any changes on mobile devices like the increasing popular mini-laptops and MIDs (mobile Internet devices).

You see, killing Internet Explorer isn't really Chrome's goal. No, killing Microsoft Office is Chrome's goal.

Chrome is open source. Its good features will soon be adopted by Firefox and other open-source browsers. Then, running on top of Windows, Mac OS, or Linux, Chrome, and the open-source browsers that take up its features, will provide the gateway on PCs and other computing devices to fast, efficient and safe Web-based applications.

Great free Web applications or pricey Office applications... Hmmm... Ballmer and the rest of the Microsoft crew should be worried. Very worried.

 

Related News and Blogs

What People Are Saying

btw

"..memory leakage problems that cause other browsers to slow down the longer you run them as they slowly but surely eat up all available memory."
This is a gross statement for many reasons - who proved that Chrome has no memory leaks at all?
1) If so - it means that Chrome has no bugs (do I have to prove that since it's in beta it's very likely that it has hundreds of bugs?) or will have no bugs - can you guarantee that? Can Google? Neither can, take every big peace of software from any company and you'll find bugs even in final versions.
2) You have to go through third party (professional and unbiased) tests to say something like this.
3) A JVM does not mean flawless memory management, Java has a JVM as well and I can tell you (being a Java developer) - there's no Java VM I'm aware about that were bug free, besides, it only "tries" to not let the memory leak, and in a lot of cases the JVM has no way to prevent that - it's up to the programmer how he uses the resources.

sounds like vista

The explanation of why Google Chrome takes (much) more memory but in the long run actually pays off reminds me much of the excuse why M$ Vista abuses lots of memory:
"The net result is a Web browser that takes up a bit more memory when you first run it, but doesn't have the memory leakage problems that cause other browsers to slow down the longer you run them as they slowly but surely eat up all available memory."

ma pravdu

Taky se mi zda, ze chrome je pouze prostredi pro beh aplikaci googlu. Nemyslim, ze by firefox, ie nebo operu nejak vic atakoval. Ma rychle nacitani/provadeni javaskriptu, takze je pripraven na google apps

Why do people leave

Why do people leave non-English comments on an English web site for an article written in English, and where all other comments are in English? I know there are some people who are overly proud of their country and their language but this is just completely stupid. It's like you have schitzphrenia or something and just go around talking to yourself. Really, what is the point in making a comment in another language here? You obviously can read the article, so why not make the comment in English? I can't believe anyone would leave a comment on an article that they can't read and understand. But I guess goofier things have happened.

It always seems to amaze me

It always seems to amaze me why people think someone cares about replacing Office in the enterprise (both small and big).

The real challenge today is enterprise software, and not Office.

If you think about it financially, its pretty obvious that a small business will have the 400$ a user (which is by far cheaper if you combine the payed subscription for different WEB 2.0 technologies that try to mimic the whole package)
and won't go cheap on user productivity.

People, wake up, no manager is going to go cheap on his worker's productivity for a few hundreds bucks, just because someone released a new browser that happens to look fresher than the rest. (and please, don't sell me this "Office is overcrowded with features story again")

The only thing that changes is that Google is first to realize that offline is important, just as online, and that with all the computing power, it still makes perfect sense to use this machine power that is already available on our laptops.

I don't think Microsoft needs to worry....

Web-based documents have been out for a very long time and I have yet to see evidence of a stampede to such new means of doing business. Hey, I even recommended using web-based docs to my supervisor, but for me personally, when I wanted to write a memo thereafter, I turned to Microsoft Office. When I wanted to put together a simple spreadsheet, Excel it was. My last presentation was done in Powerpoint and my next one will likely be done in that software package, too. If Google is aiming at Office, its a misfire.

Give it a few more years and then people will be ready...just about the time when Microsoft comes out with its new concept OS. Sorry guys; hope in vain for the Big MS' death .

Javascript Compiler

If this is true, then this is something I can get excited about; especially since this is open source. No more using the MS script engine in my Desktop apps!

not only M$ should be worried...

Nice article,

but, I think that not only M$ should be worried about what is happening but the whole OS community..

See...:

SuSE ---> Novell --> M$
KDE ---> Trolltech --> Nokia
Mysql, openoffice, java --> SUN
and now Mozilla --> Google !??!?

Now not only M$ is worried... Everybody should be worried!!

gatuus

I love it

Everything google makes is great, they just keep making working on a pc a better and better experience! Keep it up!

Good concepts, and new concepts

Sun Microsystems introduced the JAVA technologies around 1990. Their credo was to provide a development system agnostic with respect to the underlying OS. The Java Virtual Machine completelly hided all the OS details, so why stay with Windows ?
They partially succeeded, they partially failed: who's running a 100% JAVA desktop today ?

Google Chrome logics is to decouple the browsing experience from the presentation layer. Integrate the memory management, the processes, the security, ... into a single environment. Provide and unify the widgets. This way, you don't need the OS, the rendering layer, the desktop manager. You don't need applications either, everything can be managed through the internal engine (the gears).

So ? Windows killer ? Office killer ? Let's take an appointment on Sep. 1st, 2018. There are good concepts and new concepts in Chrome. We'll see if good concepts are new, and new concepts good.