3 ms·
Does anyone know if the native client is based on an abstract specification, or purely Chrome-dependent? In other words, is there a chance that other browsers
by lukev 16y ago
Does anyone know if the native client is based on an abstract specification, or purely Chrome-dependent?
In other words, is there a chance that other browsers might implement it in the future as well, allowing web developers to write client-side applications in any language that can compile to native code, not just Javascript?
If so... the day when one can actually write and deliver any type of application through the browser, with no penalty, might actually be on the horizon.
People have talked about how webapps are going to kill traditional software for the next decade. If the relevant browsers implemented this, could it finally actually happen?
- wmf 16y agoHere's the source code; I'm sure other browsers are welcome to use it. http://code.google.com/p/nativeclient/wiki/Source http://code.google.com/p/nativeclient/wiki/Source
- xtacy 16y ago> _People have talked about how webapps are going to kill traditional software for the next decade. If the relevant browsers implemented this, could it finally actually happen?_ I would say that the difference between webapps and desktop apps will disappear.
- jcl 16y agoIn fact, Native Client started as a browser plugin for Firefox, so portions of it certainly could be integrated into other browsers. However, the developers have moved from the plugin to direct browser integration to overcome limitations in the plugin API. Presumably similar integration would be necessary in other browsers to achieve the same level of functionality. http://groups.google.com/group/native-client-announce/browse_thread/thread/b7818521f855f708/82e6ac9cb4d34be4?lnk=gst&q=plugin#82e6ac9cb4d34be4 http://groups.google.com/group/native-client-announce/browse...