News for hackers. Stuff that matters.
Re:A Taste of JavaScript's New Parallel Primitives by kbenson on Thursday May 05, 2016 @01:36PM (#11638135)
> This leads to the following situation where the main program and the worker both reference the same memory, which doesn’t belong to either of them:

If only Mozilla had some technology that could deal with ownership of memory...

Seriously, if rust doesn't have an ASM.js optimized target yet, it really should.

Re:A Taste of JavaScript's New Parallel Primitives by izym on Thursday May 05, 2016 @03:14PM (#11638930)
I would be very surprised if Rust doesn't target WebAssembly sometime in the future. It's just such a good fit. If I remember correctly there are already talks about doing MIR->WASM.
Re:A Taste of JavaScript's New Parallel Primitives by spicyj on Thursday May 05, 2016 @08:09PM (#11640709)
Re:A Taste of JavaScript's New Parallel Primitives by kibwen on Thursday May 05, 2016 @09:39PM (#11641103)
We Rust folk have definitely got plans in this space. :)
Re:A Taste of JavaScript's New Parallel Primitives by seibelj on Thursday May 05, 2016 @02:13PM (#11638470)
If rust can be compiled to LLVM, then emscripten can be the backend to asm JS
Re:A Taste of JavaScript's New Parallel Primitives by steveklabnik on Thursday May 05, 2016 @02:30PM (#11638607)
The issue is emscripten uses a different LLVM version than we do; so it can work, but it's got some rough edges.

We want both compile to JS and compile to wasm to work well, the work just isn't done yet.