Google Chrome OS goes native (code)
We hate plug-ins. Except our own
A plug-in is a plug-in
"I don't see really what [Native Client] brings. I think it goes against what we're aiming for - which is to offer the web browser as the application platform."
This, Bolstad says, is the best way to battle the performance of local applications. "The thing that the web browser has going for it is that it's portable," he continues. "You can write cross-platform web applications and expect to get near-native execution speeds. Maybe not today but it's not far away."
The Native Client plug-in is available for other browsers, including Opera and Firefox. But it's still a plug-in. And it's not the only one. Google has also released its own 3D browser plug-in, O3D.
"The web’s main attractions are platform independence and instant deployment. Yet the industry’s obsession with moving every desktop application online is provoking plugin development which negates the advantages," writes Craig Buckler, director of OptimalWorks, a UK-based website-building consultant.
"Relying on a plugin violates platform independence. Creating a Go-based client-side application will almost certainly tie you to Google Chrome since NaCl will never be available for all OS and browser combinations. Many web applications still rely on IE because ActiveX was used - even though Chrome and Firefox have ActiveX implementations."
Then, of course, there's the security issue.
Sponsored: Okta Security: Technical White Paper