Newsletters

Select newsletters below and click the button to sign up!

Boston News NY News
DC News Internet Daily
SiliconValley News
InternetNews Business Report




Become a Marketplace Partner



Partner With Us















Internetnews Bloggers

Recent Entries

Archives

October 2009
Sun Mon Tue Wed Thu Fri Sat
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Monthly Archives

Search The Blog

Netstat -vat by Sean Michael Kerner (bio)

A command line view of IT



Google Chrome goes Native in 4.0.220.1

googlechromologo.jpg
From the "ActiveX Look-alike' files:

Google is now out with Chrome dev-channel version 4.0.220.1 which is notable for one primary reason -- Native Client.

The 4.0.220.1 version is the first Chrome release to include Native Client as a built-in client for Windows. Native Client is a technology that will enable the browser to run code over the web (not just JavaScript or Java) but regular software.

The implications for Google are huge as it could enable a new generation of speedier, feature-rich Google Apps (and eventually other apps from other vendors).

Google first announced that they were moving Native Client out of research mode and into production in June and here we are four months later with the first Windows build.

Native Client is not without it's challenges from a number of perspectives.

The most obvious challenge are the inherent security issues that native client brings to the table. Sure, Google has this nice process isolation for Chrome, but with applications, will that same isolation hold out against the myriad of app threats that exist today?

The other challenge is to get over the notion (right or wrong) that Native Client is simply Google's attempt to replicate Microsoft's ActiveX.

That's right, ActiveX originally held the same promise that Google is now making, a decade later for Native Client. ActiveX over the last decade has been hammered by all kinds of security issues, which has forced Micrsoft to patch and modify ActiveX, IE and Windows.

Google will have the benefit of learning from ActiveX's flaws, but many of the same challenges remain.

The final issue in my view that Google will have to deal with is the idea that Native Client is a Google-only technology.

ActiveX became successful because of Microsoft's massive partner ecosystem that adopted the technology widely. IE also had a dominant market share. Google for all its power and wealth doesn't have the same kind of third party ecosystem and Chrome does not enjoy the same market position as IE.

| Comments (0) | TrackBacks (0) | Share

0 TrackBacks

Listed below are links to blogs that reference this entry: Google Chrome goes Native in 4.0.220.1.

TrackBack URL for this entry: https://swarm.jupitermedia.com/mt-tb.cgi/9016

Leave a comment