Business

Google Re-Re-Ignites the Browser Wars

profwhat.

Posted to Business on Thu Sep 04, 2008 at 03:13:25 AM EST (promoted by 1fastdog). RSS.

Meeting a need that no one realized they had, Google has unleashed a new web browser upon the world: Chrome.  It offers a clean interface, really fast performance, crash protection, fast performance, an Opera-like "speed dial," and also, did I mention, fast performance.

Remarkably, in 2004 Google CEO Eric Schmidt denied Google would ever launch a browser.  Yet, this project got the go-ahead in 2006, and a huge Google team has been working on it ever since.  The strategy (as declared by Google in a sort of online comic book) seems to be that Google wants to accelerate the move of the desktop computer into the cloud by providing a browser that can run JavaScript really, really fast.  Chrome runs on a new JavaScript engine, named V8, which (Google claims) can run JavaScript 8 to 10 times faster than other browsers.  This, hopefully, will make using JavaScript-based web applications--notably, web-based word processors like Zoho Writer or Google's own Google Docs--less painful to use.  That, in turn, will cut into Microsoft's cash cow, Office sales.

So, it's 2008, and the browser wars are back.  Internet Explorer 7 has 47% of the market; the seven-year-old Internet Explorer 6 still holds 25%; and Firefox has around 19%.  Microsoft just released IE 8, and Firefox 3.1 should be out before long.  Harried web developers have long decried the need to test their web pages against five browsers (add Apple's Safari and the cult browser Opera to that list), although Chrome should render pages the same way that Safari does.  The big loser here (if anything is to be lost) might be Firefox; Chrome is also going to be open source, so it might leech away some of the love Firefox receives from that community.

Tags: written by profwhat, edited by 1fastdog, Chrome, Google, browsers, Firefox, IE (all tags)

This story: 20 comments (1 from subqueue)
Post a Comment
2

The elephant in the room...

port1080.

Thu Sep 04, 2008 at 07:58:12 AM EST

5.00 (astute)

...is not javascript, but Flash.  Adobe has only taken pains to make sure Flash runs reasonably well on IE on Windows.  Sure, it runs on other platforms and browsers, but it generally does so quite poorly and it certainly loves to hog resources, crash browsers, etc, etc.  Unless Chrome can figure out a way to bribe Adobe to make Flash world class, Chrome will get the same complaints all the other browsers do.  What this really points to is the need to incorporate the capabilities of Flash into the web standards, so that the next round of browsers doesn't need to rely on a third party plugin controlled by a for-profit company to do the things that people seem to want (for whatever reason - I think I could do without about 95% of flash content, or find a good substitute without using flash).

13

^ 2

Re: The elephant in the room...

joshv.

Thu Sep 04, 2008 at 04:56:57 PM EST

4.00 (astute)

Make no bones about it, Chrome is meant to enable a platform that will directly compete with with Flash - specifically, note the new "V8" javascript engine, which compiles javascript to native code and has much improved garbage collection.  Google explicitly states that this is a move to make javascript faster and more robust, so that more complex application can be built using it.

Now, if somebody could come up with a programming model/environment for HTML/DOM/Javascript that didn't suck ass.

4

Everything Google Does Is Twice As Something

MayorBob.

Thu Sep 04, 2008 at 09:51:44 AM EST

5.00 (funny)

I tried to download it and ended up receiving a "Fatal Error Four" message. I guess that's twice as worse as Fatal Error Two.

Illegitimi non carborundum.

6

Unimpressive

T Slothrop.

Thu Sep 04, 2008 at 11:47:35 AM EST

5.00 (informative, astute)

I've been playing with it for two days now (I'm writing this post with it), and it doesn't thrill me.

It does look great. The interface is very clean and minimalist, yet all the features I use regularly are easy to get to. But as someone else has already pointed out, it cannot handle Flash for shit. The hurricane tracker app on the msnbc site (thanks Mayor!) loads but then freezes. A spot check of several sites that rely heavily on Flash demonstrates similarly abysmal performance.

It doesn't appear to run javascript any faster than Firefox, either. I haven't tried it with any of google's web-based apps, but the sites I frequent that use a lot of javascript don't seem to be any faster.

The interface is cool, but it will take a lot more than that to compel me to dump Firefox.

{Insert amusing quotation here}

15

^ 6

Re: Unimpressive

jwb.

Thu Sep 04, 2008 at 07:07:03 PM EST

5.00 (informative, astute)

I'm not impressed either.  The press and the bloggers are uncritically repeating the "8-10x faster" claims from Google's press release, but the benchmarks don't bear it out.  On general purpose benchmarks like SunSpider Chrome is fast, but not crazy fast.  It's about on par with Firefox 3.1 on my computer.  In a number of DOM benchmarks it actually loses to Firefox 3.1 and Safari 4.  The only benchmark that supports the 10x claim is one Google themselves wrote, which consists almost entirely of recursion.  It's not a realistic picture of browser performance.

I foresee a real problem for Chrome because it looks like they spent all their effort on JavaScript execution speed and process separation, but didn't address WebKits serious memory usage problems.  Firefox has tackled both size and speed problems in 3 and 3.1 respectively.  Firefox 3's memory usage tends to be constant over time while Chrome's memory use increases quite linearly if you leave it running.  They're going to have to address WebKit's memory management before it will be a serious application platform.

That said, the KHTML people should be proud that they've now spawned three completely respectable browsers: Konqueror, Safari, and Chrome.  Despite the decade of development behind Mozilla, only Mozilla's own projects (Firefox, Thunderbird, and Camino) use their engine.  The third-party people like Songbird don't have any traction.

Microsoft, on the other hand, should hang their heads in shame.  Internet Explorer 8 is about 5 times slower than any of Chrome, Firefox 3.1, or Safari 4.  And Internet Explorer 7 is twelve times slower than its contemporaries Firefox 3 and Safari 3.  Shameful.

9

^ 6

Re: Unimpressive

zyxwvutsr.

Thu Sep 04, 2008 at 02:18:57 PM EST

none

Regarding javascript, I read somewhere (can't recall where at the moment) that they're working on optimizing the scripting performance, but that the beta isn't there yet.

11

^ 9

Re: Unimpressive

T Slothrop.

Thu Sep 04, 2008 at 02:55:42 PM EST

none

Well that would make sense. I downloaded it largely on what was supposed to be its screaming performance on javascript, and I knew that I just wasn't seeing anything any better than Firefox 3. To be fair, it was certainly no worse than FF3 either, but it sure didn't live up to its hype.

{Insert amusing quotation here}

12

^ 11

Re: Unimpressive

profwhat.

Thu Sep 04, 2008 at 03:05:05 PM EST

none

JavaScript performance is difficult to measure and compare, but Chrome does very well in major benchmarks.  Your actual user experience may vary, of course, because life doesn't happen in a test-tube.

One page where I notice faster JavaScript performance, for example, is TNT's "Tags" page, when you click on a column title to sort by that column.  Saves about a second or two.

10

The little things

profwhat.

Thu Sep 04, 2008 at 02:51:10 PM EST

5.00 (informative)

Google Chrome has lots of little touches that aren't immediately apparent:

  • It saves copies of the text of every page you visit.  Later, if you type a word that appeared in that page into your location bar, it will let you find that page.  So, if you're idly surfing one day and read an article about Tesla's energy coil, and two days later you want to find that article again but all you can remember is that it contained the word "telluric," just type that word into the location bar and your local history gets searched automatically.  Firefox, as far as I know, only searches through past URLs and title tags.

  • Go to any site with a "search" option, like news.yahoo.com (or treesandthings.com).  Perform one search.  Chrome now knows that this is a searchable site, and it can search for you.  In the location bar, type "news.yahoo.com" (or use autocompletion if that's too many characters for you), then hit tab.  You get the ability to directly query news.yahoo.com for an article.  This is huge; there's no need to write those stupid plug-in things, or to persuade users to download yours.  Do one search on treesandthings.com, and then from then on the browser is smart enough to do future searches for you!

  • For people who do web development, it has a rough version of Firebug built-in.  RIght-click on anything and say "inspect element."  Cool.

There are some downsides.  No Linux; it has few privacy controls; every keystroke in the location bar is sent to Google (or the search engine of your choice); and no adblock.  I haven't had the Flash problems other have reported, but then I try to avoid Flash sites anyway.

16

^ 10

Re: The little things

rumata.

Thu Sep 04, 2008 at 09:28:53 PM EST

5.00 (informative, informative)

[Chrome] saves copies of the text of every page you visit [and allows you to search it]

Opera does this as well, without keeping https stuff around.

In the location bar, type "news.yahoo.com" (or use autocompletion if that's too many characters for you), then hit tab.  You get the ability to directly query news.yahoo.com for an article.

Opera does this better, although it requires some manual setup: Right-click into a text-box, select "Create Search", give it a short cut (say "ny" for your "news.yahoo.com" example) and of you go.

Ctrl-t opens a new tab with an empty location bar, cursor in the bar, type "ny democratic convention" and hit enter.

I've set up:
-gs  -- google scholar
-gm  -- google maps
-th/tl  -- trip planner from home / our lab
-d  -- my favourite dictionary (dict.leo.com)
-r  -- recipes (cooking for engineers :-p)

Ok, enough Opera propaganda for now.

Cheers,
Michael

PS I've recently discovered that it actually does have a spell-checker

17

^ 16

Re: The little things

jwb.

Thu Sep 04, 2008 at 09:47:08 PM EST

5.00 (funny)

The feature you describe has been in Netscape/Mozilla since 1995. I don't think it's widely used though. Probably about as popular as about:minibuffer.

18

^ 16

Re: The little things

profwhat.

Thu Sep 04, 2008 at 10:38:18 PM EST

none

Firefox has the same ability to create a search shortcut by right-clicking a field.  The interface is awful, though; you create something called a "Quick Search," which you have to stick somewhere into your bookmarks hierarchy, even though you'll never select it from the bookmarks menu, and then you have to remember the abbreviation you invented, which I never can.  Chrome doesn't make you do anything; it just remembers.

19

^ 18

Re: The little things

thefadd.

Fri Sep 05, 2008 at 01:15:44 AM EST

none

Chrome doesn't make you do anything; it just remembers.

Which always makes me think of the Volkswagen Beetle that had the license plate: FEATURE.

It is easy to buy small plaster models of what you think life is like.

14

^ 10

Re: The little things

joshv.

Thu Sep 04, 2008 at 05:02:52 PM EST

4.50 (informative, informative)

"It saves copies of the text of every page you visit."

This appears to include copies of your bank balances and other information from SSL encrypted pages.  http://www.tgdaily.com/content/view/39176/108/

20

serious doubts

DEMachina.

Fri Sep 05, 2008 at 09:37:36 AM EST

4.50 (informative, astute)

I have serious about about Chrome.

One, privacy.  Even though Google says they'll change the EULA after people realized they were giving Google access to everything, there's still a big concern.  If you leave "suggest sites" turned on, Google will have access to everything you type in the omnibar, whether you submit it or not.

Two, speed.  All the benchmarks I've seen show Chrome's multiprocess approach takes up more memory.  Google claims it'll end up being less in the long run, but how much of that benefits normal users?  Two, Firefox's new JavaScript engine is faster.

Three, security.  As much as Google has lauded the security of Chrome, there are already reported vulnerabilities.  For one, they used an old version of WebKit as the rendering engine, one which has a well-known security hole.  This has since been patched in Safari, but not in Chrome.  Seriously?

Q: What do you think of western civilization? Gandhi: I think it would be a good idea.

1

Re: Google Re-Re-Ignites the Browser Wars

wetkarma.

Thu Sep 04, 2008 at 07:01:48 AM EST

none

Currently there seems to be quite onerous licensing terms with the use of Chrome - where google lays claim to all content (eg. this post) if it was created via Chrome.

Its my expectation that this was some sort of cut-and-past boilerplate glitch which will soon be rectified. If however, they meant to do this, I don't see a reason why I'd use the browser - no matter how fast it is.

Memory is a strange bell, jubilee and knell.

3

^ 1

Re: Google Re-Re-Ignites the Browser Wars

zyxwvutsr.

Thu Sep 04, 2008 at 08:21:41 AM EST

5.00 (astute, funny)

How do you expect Google to deliver the ads you need unless you let them have your data?

5

^ 1

Re: Google Re-Re-Ignites the Browser Wars

Lou.

Thu Sep 04, 2008 at 11:36:06 AM EST

none

Rest assured though that they won't use any of the submitted stuff for evil purposes.

It's the end of the world as we know it, and I feel fine

7

^ 1

terms yanked

1fastdog.

Thu Sep 04, 2008 at 01:08:56 PM EST

none

Currently there seems to be quite onerous licensing terms with the use of Chrome - where google lays claim to all content (eg. this post) if it was created via Chrome.

Those clauses have been terminated:

Google representative Rebecca Ward, head lawyer for Chrome, says the inclusion of Section 11 was a simple oversight, caused by the company's proclivity for releasing multiple products under a single, "Universal" Terms of Service.

"Sometimes, as in the case of Google Chrome, this means that the legal terms for a specific product may include terms that don't apply well to the use of that product," she said Tuesday. "We are working quickly to remove language from Section 11 of the current Google Chrome terms of service."

Even better, Ward says the change will be applied "retroactively" to "all users who have downloaded Google Chrome."

Methinks it was the very loud and very early backlash against the terms rather than oversight on Google's part, but who knows?

Somewhere in my soul, there's always Rock -n- Roll... Joe Strummer

8

^ 7

Re: terms yanked

profwhat.

Thu Sep 04, 2008 at 01:17:21 PM EST

none

I don't know whether to be impressed with Google's speed in fixing the problem, or astounded at how obvious the problem was to begin with.

This story: 20 comments (1 from subqueue)
Post a Comment