If anyone from Cheerp reads this, I use emscripten (https://github.com/kripken/emscripten) at the moment, is Cheerp any better ?
Specifically does it compile faster, generates a smaller final .js output, or produce "faster" code ?
Specifically does it compile faster, generates a smaller final .js output, or produce "faster" code ?
Dynamic memory management. C++ objects are translated directly to JS objects, without the proxy of an emulated, flat memory space. Allow your applications to exploit the JavaScript VM garbage collector and co-exist with fair, on-demand memory allocation.
I don't think that's a good thing though, since the reason why emscripten compiled code is fast is because it has a flat memory space and doesn't create expensive JS objects.
Only advantage IMHO is that you don't need to allocate a big chunk of memory ahead of time (although I think emscripten still allows a growable heap as an option, but with a performance penalty).
http://mozakai.blogspot.co.uk/2013/11/c-to-javascript-emscri...
I may do a followup post now, since Cheerp is at 1.0. Seems like a good time to do some benchmarking.
An integrated code minimizer is in the pipeline for release 1.1, and for the medium term we are working on an optimizer which cuts away unneeded libc++ initialization, which is preventing the dead code eliminator from pruning the non-useful libc++ code (which is a great part of that 1.7Mb).
So, expect big improvements in this area!
Disclaimer: I am one of Leaning Technologies founders.