Sep 03 2008

Google cannot see the future

Published by Aaron Worsham at 2:35 pm under News & Notes, Opinion, Tips

Yesterday morning, Google made a little announcementYou may have heard of it already.  Tuesday’s blog reader was like a million tiny voices all calling out the same word.  That cacophony continued on through today and I suspect it will remain as such throughout the month, or at least until Apple releases something shiny.  So much has been made of this small release, that I have vowed not to refer to it by name in this post.

The internets chattier apologists are already manuvering into position to hand Google the gold-painted plastic trophy of ‘Best Browser Ever‘ despite its current 0% adoption share, buggy Javascript, or total lack of support for my fruit-themed notebook.  I think this is a mistake.

Remember how quick we were to jump over to Microsoft’s camp when they announced IE would free us from paying for a browser?  Or when Firefox shook us out of that complacent stupor, slapped our faces and told us we didn’t need 10 windows open at once and that hey, we might like these super useful user created plugins?

Google isn’t putting out this reflective metallic bauble because it want’s to convert the masses.  They know they cannot see into the future, so any effort to corner the browser market is likely effort in vain.  Overlooked in the hype was a message that I heard loud and clear - and it was coming from Google.  Somewhere around the discussion of open sourcing the software, they made a very strange statement.  ‘We want others to copy our ideas, improve them, do it better, and reinvent the internet for us all’.

If that is true, why make their own browser?  Why not simply put their mental might behind Firefox, which is fully open sourced and free to fork off?  I truly don’t know, though I suspect that is what they did.  Looking under the hood (or more accurately read under the press releases), much of the plumbing is changed.  Multi-process based instead of single process with rewritten javascript JIT compiler makes the app different from firefox as steam locomotion is from gas combustion.  Still, there are pieces that are coming from Mozilla and WebKit which makes this more of a reinterpretation than a reinvention.  WebKit is the JavaScript renderer used in Safari and iPhone, so I would suspect to see this also be adopted in Google’s mobile OS, Android, as well.

I can’t say that Google will not come out ahead of the pact with this mirror-like offering.  Once they get their sea legs they will have their half-tillion dollar geek cred behind them.  Even so, I can say is that no one should be calling this race over.  The brower wars are heating up again and only the gentle sob of your company’s web designer is heard above the blogging din to mark the occasion.  Hell, that ‘Best Browser Ever’ trophy was stolen anyway, years ago, by the Opera fanatics.  Rumor says it is buried somewhere in Norway.

Sphere: Related Content

4 Responses to “Google cannot see the future”

  1. Thomas Hansenon 03 Sep 2008 at 6:14 pm

    Errhh…
    Google Chrome (I said it) actually have less than 48 hours after release between 1 and 3 percent market share… ;)

  2. Leonaut.comon 04 Sep 2008 at 1:26 am

    Google cannot see the future…

    Yesterday morning, Google made a little announcement. You may have heard of it already. Tuesday’s blog reader was like a million tiny voices all calling out the same word. That cacophony continued on through today and I suspect it will remain as suc…

  3. tonon 05 Sep 2008 at 1:37 pm

    “WebKit is the JavaScript renderer ” Ummm … don’t you mean rendering engine? Javascript isn’t rendered it’s interpreted or in the case of V8 complied.

  4. meon 05 Sep 2008 at 1:39 pm

    “WebKit is the JavaScript renderer”… Whats that?

Trackback URI | Comments RSS

Leave a Reply