kevin curtis wrote: > Python has a concept 'extension modules' where module can be > implemented in c/c++. Also the idea of running native code in the > browser has been put forward by Google's native client for running x86 > in the client. MS - i think - are researching something similar.
The idea of running native code securely in the browser is speculative and unproven. Nothing should be standardized in this area unless and until such approaches can be demonstrated to have a reasonable chance of resisting attack. To do so would be to repeat previous mistakes that have led to the insecure web we currently have. > c/c++ isn't going anywhere and the relationship between ecmascript and > c/c++ is interesting. Are there any proposals for something like > 'extension modules' for ES6 or do the variations in the engine > implementations preclude such a thing? As far as a foreign function interface for non-web uses of JavaScript is concerned, that is something that might in principle be worth standardizing (probably separately from ES6). However, the internal C/C++ interfaces typically used by current JS implementations are highly error-prone, make too many assumptions about implementation details (particularly memory management), and are not suitable for wider use. -- David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
