3 ms·
The main use for something like LLJS is to allow you to target asm.js with new code that you write. It's true that it's probably not the best idea to completely
by jlongster 14y ago
The main use for something like LLJS is to allow you to target asm.js with new code that you write. It's true that it's probably not the best idea to completely rewrite a 3d engine in it (right now), but it gives you a quick way to rewrite core parts of an intensive app (like a 3d game) for high performance. There are "inner loops" that could benefit from a small amount of LLJS.
As the post says, it's a proof of concept and a way to open up asm.js to people who want to tinker with it without compiling C code with emscripten.
- kayoone 14y agoI see, so the main benefit vs compiling c to asm.js is that the development process is easier because you dont need to manually compile. Sounds interesting to use as a scripting language inside a c based game engine. So the core of the engine would be directly compiled to asm.js while the game logic scripting could be done in LLJS to be able to live-test your game.
- jlongster 14y agoThat's certainly a possibility! It would be neat to see powerful debugging tools develop, after the language stabilizes. I also like the idea of somehow linking it with emscripten-compiled code so that it can be used as a sort of scripting language. I'd like to explore the possibility of porting some of the C toolchain to the browser too, though. It's possible that it could be quite successful, and in that case LLJS would target people who just want to write small parts of there app for asm.js.
- kayoone 14y agosounds really exciting, keep up the great work!