Image credit: dropit2entrecard.blogspot.com
Something fell off our plate amid the late craze in tech reporting, especially with Google buying Motorola and HP abandoning PC biz and webOS devices. That doesn’t mean this little nugget is not worthy your attention, quite the contrary. Three years ago, Google mentioned it would eventually enable the so-called native code execution in Chrome. The latest beta of Chrome 14, unleashed a week ago, now supports this functionality, the Google Operating System blog has discovered.
In Layman’s terms, native code execution lets the Chrome browser run snippets of web code specifically optimized for your computer’s processor rather than analyze, interpret and painstakingly turn HTML code line by line into a machine-readable format – that takes a lot of time, slowing down code execution as a result.
Google’s definition simply states the technique lets developers “build web applications that seamlessly execute native compiled code inside the browser”. For our tech-savvy readers, Google outlined some of the benefits of this technique in the announcement blog post three years ago:
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. At Google we’re always trying to make the web a better platform. That’s why we’re working on Native Client, a technology that aims to give web developers access to the full power of the client’s CPU while maintaining the browser neutrality, OS portability and safety that people expect from web applications.
The stable Chrome 14 release is expected within a month, when native code execution will become standard feature for the 160 million active Chrome users, as of May 11. So, why should you care? Read on…