It could be improved a bit, but the real issue is that JavaScript is a high-level, garbage-collected, dynamic programming language, while C is a low-level, memory-unsafe, type-unsafe, statically compiled programming language.
I have heard a few ideas floating around on how this could be improved, by using a radical redesign of js-ctypes based on asm.js/WebAsm, but at the moment, I don't think that anybody is working on it. Cheers, David On 20/11/15 12:03, Philip Chee wrote: > On 18/11/2015 16:04, David Rajchenbach-Teller wrote: >> Well, the main problem is that js-ctypes is very hard to use, even >> harder to use without causing memory leaks or crashing the process. >> Think the worst parts of both C and JavaScript together. > > Are these problems inherent in ctypes or is it just that our > implementation is broken? _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
