16 Comments

Summary:

With Google’s release of a software platform known as Native Client, the company has moved even closer to fulfilling the early promise of a “web operating system” — a vision originally offered by browser-software pioneer Netscape Communications. By allowing browsers to run code in the language understood by a user’s PC, browser-based software and services will run faster and be able to offer more functionality than they can now — and browser-based services that could replicate all of the features of a desktop application would become a reality.

With the release on Monday of a software platform known as Native Client, Google has moved even closer to fulfilling the early promise of a “web operating system” — a vision originally offered by browser-software pioneer Netscape Communications.

Over a decade ago, Netscape was the technology name that made users smile and competitors tremble. And one of the things that kept Microsoft awake at night was the fear that Marc Andreessen’s company might be able to turn the browser into a kind of web OS. Using a new software scripting language known as Java, the theory went, Netscape would be able to offer services and features through the web browser that would compete head on with software installed on PCs.

That fear was a big part of the impetus for Bill Gates’s famous “Internet tidal wave” memo in 1995, and it was also a big reason why Microsoft started pushing its own scripting language for the browser, known as ActiveX. As it turned out, Netscape was never able to follow through on the early promise of a browser OS. Not only was Java too clunky, insecure and ill-suited to the purpose, but Netscape never really took advantage of it, and the browser wars that Microsoft triggered with the release of Internet Explorer soon turned in the software giant’s favor, as Netscape became bloated and unfocused.

Now, Google is offering its own scripting language known as Native Client, which the company no doubt hopes will be seen by developers as a friendlier version of ActiveX. What it will allow browsers to do is run code in the language understood by a user’s PC, rather than having to translate everything on the fly. In a nutshell, that means browser-based software and services will run faster and be able to offer more functionality than they can now. Browser-based services that could replicate all of the features of a desktop application would become a reality.

As several observers have noted, the combination of Google’s new Chrome browser, its Gears software — which allows web apps to store data for offline use and synchronize it later — and the Native Client language makes for something that is awfully close to being a web OS. Applications and services could run on any computer, storing data whenever an Internet connection wasn’t available and effectively erasing the boundaries between desktop and web. And all it requires, of course, is that everyone adopt and adhere to Google’s new language and standard (both Microsoft and Adobe have been trying something similar with Silverlight and Flash/AIR).

Is the world ready for a Google-ized version of ActiveX? Perhaps not. But if the company does manage to get enough support for Native Client, the web OS could become a reality — and the knife that Google is already holding to Microsoft’s neck with its web apps could cut a little deeper.

  1. “…the knife that Google is already holding to Microsoft’s neck with its web apps could cut a little deeper.”

    The most well written sentence I have read in a post all day. Thank you.

    Keep hope alive!

    Share
  2. Notaprogrammer Tuesday, December 9, 2008

    Wow. Didn’t know that Java was a scripting language. Netscape released their Mosaic browser before Java was even released. Perhaps the writer meant javascript? I know it’s tough in this day and age to find good technical writers, but this is poor domain knowledge, as well as poor editorial work.

    Share
  3. You fail to note that ActiveX never really “caught on”. As a Windows-only technology, you really can’t deploy it on the web, or lots of people won’t be able to use your site.

    Share
  4. @notaprogrammer: thanks for catching that in the description of Java — I should have just said “programming language” and left it at that. And @TomB, that is a great point about ActiveX, and one of the main reasons it didn’t take off as much as it probably could have — and a significant difference between it and Native Client as well.

    And @Todd, thanks for the compliment. Glad you enjoyed it :-)

    Share
  5. Will very interesting so see how Native Client compares to the method of combining adobe flex with c++ for web appz. Wow the possibilities that Native Client will opening for the web with rich powerful fast web applications.

    Share
  6. Is anyone else worried about the security implications of this? ActiveX is notorious for exposing the end user to more threats. I’d like to hear more from the security community referenced here: http://googleonlinesecurity.blogspot.com/2008/12/native-client-technology-for-running.html

    Share
  7. Security is my main question as well…the downfall of ActiveX was indeed security…

    can someone please post a follow up regarding how the security levels are intended to match up against the ever growing abilities to counter new programs?

    Thanks

    Share
  8. Great post. The web app vs desktop app is the most central conflict in all of internet history, and it began long before Web 2.0 was coined. Tim O’Reilly has written plenty about this, great read.

    Share
  9. I know they will concentrate on Windows first… but really they should focus on a version for Linux. At last, a clear alternative to Windows. Bring it!

    Share
  10. [...] thought it was interesting to see what is happening to the browser world. I don’t think this GigaOm article is that well written but it does kick off a nice discussion. Clearly Netscape was on the right [...]

    Share

Comments have been disabled for this post