"Based on our experience to date, we believe that the basic architecture of our system is sound and the implementation is supportable," Chen wrote. "So now we are undertaking a number of tasks to transition Native Client from a research technology to a development platform."Among those tasks, is getting the code into the Chromium project (Chromium is Google's open source development effort that leads to Chrome browser releases). Currently the Native Client is being implemented as a browser plug-in, though Google is planning on fully integrating the technology into the core of Chrome.
"Finally, some of you have asked when Native Client will be ready for end-users," Chen wrote. "In this context, we recognize that there is well-justified resistance to installing browser plug-ins. For this reason we have a strong preference for delivering Native Client pre-installed or built into the browser, and we'll be focusing on that as our main strategy for delivering Native Client to users. Careful readers may have already noticed evidence of integration into Chromium <http://dev.chromium.org> in the Native Client source. Recognizing the many technical and non-technical challenges to browser integration, we will continue to support our NPAPI plug-in until we can deliver the system via a better alternative."It's a very powerful idea -- and one that could in my opinion could further fragment the browser market. Sure, Google will try and get the idea of native code/client standardized in HTML5, but it'll be a challenge.
Article courtesy of InternetNews.com.