3 ms·
There are other paths for Haxe, although they are probably not pretty. That is Haxe -> C++ -> Emscripten -> asm.js. Then there is another, Haxe -> Java -> GWT -
by protoduction 12y ago
There are other paths for Haxe, although they are probably not pretty. That is Haxe -> C++ -> Emscripten -> asm.js. Then there is another, Haxe -> Java -> GWT -> JS.
I think Haxe is underappreciated for areas other than game development. You can write serverside logic with it (compile to js for node.js, php, neko, java, c#, python), and target flash and js in the browser.
- sehugg 12y agoThere's also Java -> GWT -> JS, using libGDX to target iOS/Android/WebGL: http://blog.puzzlingplans.com/post/100992521086/building-a-cross-platform-game-with-libgdx-part-4 http://blog.puzzlingplans.com/post/100992521086/building-a-c...
- chii 12y agoand don't forget http://www.robovm.com/ http://www.robovm.com/
- georgemcbay 12y agoI agree. Haxe has a very vibrant community but I'm still surprised it never got bigger than it has. I used it extensively at Chumby on apps for the devices since the alternative was using ActionScript 2 (which is basically JavaScript minus the more modern features post-ECMAScript3). Given roughly the same code (minus the syntax differences for each), the Haxe compiler would run much faster than Adobe's and almost always generated faster bytecode even though I was targeting Adobe's own Flash AVM1. Plus haxe let me use all the goodies the language offers, like non-brain-dead scoping, static typing and the macro system.