4 ms·
the comments over at cnet are very ill-informed. native client allows you to run x86 assembly code (from a c compiler or even handwritten) at native speed. tha
by enki 17y ago
the comments over at cnet are very ill-informed.
native client allows you to run x86 assembly code (from a c compiler or even handwritten) at native speed. that is: no vmmon, but truly native! this is very different from JIT compilation or other "high performance" runtime environments.
http://code.google.com/p/nativeclient/ http://code.google.com/p/nativeclient/
combining this with o3d (http://code.google.com/apis/o3d/ http://code.google.com/apis/o3d/), high performance javascript and the html5 apis, will make this an extremely powerful platform.
only downside: the security model is rather hard to prove.
- eugenejen 17y agoNot only those. If the native client is a go, then we have no need for any desktop applications on x86 systems, no more dll hell on client side running x86 code. This technology maybe the stone that kills Microsoft. -- edit -- probably we still need browser and IDE and debugger on desktop. It is hard to imagine developers wants to use web apps. But maybe we will run even a disassembler in browser...
- pmjordan 17y agoWell, minus anything that would violate security policy. Which is actually most current desktop apps.
- eugenejen 17y agoYes, you are right. to access local file system. But if you read the porting guide of native client, you know there is not local file system any more. The only data they can access is same origin files. And it seems there is no reason we need to keep files in the long run, if you buy into the hype from cloud computing. But I guess that will be another 20 years...