Very interesting post from Google about their Native Code project, which is essentially a browser plug-in that lets developers execute native code on the user’s PC rather than server-side.
The Google Blog post starts like this:
“Modern PCs can execute billions of instructions per second, but today’s web applications can access only a small fraction of this computational power. If web developers could use all of this power, just imagine the rich, dynamic experiences they could create.”
That’s exactly what Microsoft has been saying for a long-time. What’s the use of having all this computational power on the PC if we run all of our computations across the cloud?
I guess you could say that Google’s approach is Services + Software, although it’s worth pointing out that the developer documentation does indicate that you can run Native Code applications without a browser. The only real difference then between the Microsoft approach and the Native Code project is that Google’s effort adopts OS and Browser portability as a core foundation of the effort.
From my read, the Native Code project will give developers far more power to exploit the desktop’s processing power than other like-efforts, the most obvious of which is Java. However, in doing so it really is going to open up a Pandora’s box of security issues and you can see from the Google blog post that security is something it admits is going to be a problem and that is going to require a community-wide effort to deal with.
Microsoft can probably quite rightly argue that for all the flack Windows gets on a security front, it is absolutely lightyears in front of an effort like Native Code.
So the question is, how important these days is OS/browser portability vs security.