News for hackers. Stuff that matters.
Re:PyPy.js: First Steps by kevingadd on Tuesday July 23, 2013 @03:05PM (#6092214)
Re:PyPy.js: First Steps by spankalee on Tuesday July 23, 2013 @10:50PM (#6094215)
I'm not sure what your point is, but so far the asm.js samples that I've seen have not indicated that compiling a runtime for a dynamic language, including memory management, GC, and JIT, are anywhere near as fast as transpiling to JS, and there are tons of complications.

lua.vm.js is running at 50% of Lua, not LuaJIT. Add to that that you can't touch the DOM from asm, and the ported VM basically has it's own heap and no way to collect cycles between Lua and JS and it's not a good solution. Much better to rely on the JS VM for memory management.

Re:PyPy.js: First Steps by kevingadd on Wednesday July 24, 2013 @10:18PM (#6100546)
Transpiled asm.js code beats the pants off non-asm.js code in almost every regard. Period. I have not seen a single case where code heavily leveraging the JS GC heap, etc. will outperform the typed array, virtual heap, etc. style even WITHOUT the benefit of asm.js's AOT compilation.

It's possible, of course, but I've never seen it. And I certainly haven't found any way to achieve it with a compiler. If you have, let me know...