emscripten

Sounds like a job for emscripten: https://github.com/kripken/emscripten/wiki

We might as well go full circle :) https://github.com/kripken/emscripten/wiki http://news.ycombinator.com/item?id=1644192

I don't know how to be more clear. I'm not talking about the technical difficulties by themselves, out of context. The technical difficulties are formidable -- but not insuperable for Google with its many engineers. I'm saying that in context of market realities, the other browsers won't use shared Google-source as the "implementation is the specification" for NaCl/Pepper, and no one can write a real NaCl/Pepper spec by which any browser could implement an independent and interoperable workalike in less than decades. So why try if the OSes can do their own non-interoperating workalikes? (And they are already doing this, from what I hear.) If safe native code on the web is mainly for plugins, there's no problem. Plugins are OS-specific today and likely to remain so, safety or no. Moving the Web VM to a more abstract level... hmm, sounds li

x86 emulation is the wrong solution to this problem because of the difficulty of interop. Compiling to bytecode at least lets you treat JS functions as FFI calls. The first project to do this was Clue in 2008 (http://cluecc.sourceforge.net/), now all the hype is about emscripten (https://github.com/kripken/emscripten) LLVM bytecode to JS compiler. Doing compilation GWT/Clojurescript style is going to reduce integration overhead. So far I haven't seen anything that integrates as well as Parenscript.

Another project in the same vein: https://github.com/kripken/emscripten/

If this works out, it basically also means Scala->JavaScript through emscripten (https://github.com/kripken/emscripten). Slow, probably, and probably with nearly impossible interfacing with the DOM and JS libraries, but still - pretty cool

Really nice... I found it interesting that you are with Mozilla considering the guy behind the llvm-to-javascript compiler works there too... https://github.com/kripken/emscripten

In theory, someone could create a common bytecode as a library. Such a library would probably use the Relooper algorithm from Emscripten (https://github.com/kripken/emscripten) and JIT the bytecode to Javascript that can then be eval'd for near Javascript-level speed.

You really need to look at Coffeescript (http://jashkenas.github.com/coffee-script/) and Emscripten (https://github.com/kripken/emscripten). I use coffeescript for all of my javascript development now and life has never been better. I've never used Emscripten in a serious capacity, but both of these projects are under very active development and show that javascript really is becoming the x86 of the web (as stated by Brendan Eich). No need for us to wait on the four big companies. Things are moving forward without them.

So now that we have https://github.com/kripken/emscripten and a reliable LLVM backend for GHC, has anyone tried compiling Haskell to JavaScript? My instinct is that the world would explode but I can't be sure.