Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale
by jerf on Wednesday April 04, 2018 @03:26PM
(#16758047)
"Erm... PSA: Rust isn't the only language that is compiling to WASM."
No, but Rust will still be sitting in a sweet spot, having many of those characteristics I named. For instance, Python compiling to WASM may be useful, but it won't have any of those advantages. Python running on WASM isn't hardly a threat to JS at all, because it won't do anything JS can't. Rust will conceivably be able to in the near term, and as I said, if it takes off and the browsers start adapting to statically-typed functions running in WASM the gap could open even more.
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale
by timClicks on Wednesday April 04, 2018 @05:10PM
(#16759130)
IIRC wasm has no GC capabilities, so Python is an unlikely source language.
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale
by steveklabnik on Wednesday April 04, 2018 @05:29PM
(#16759322)
In cases like that, you also compile the Python GC to wasm and use it. It ships with your app, adding bloat to your binary though. It does work!
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale
by timClicks on Thursday April 05, 2018 @04:29AM
(#16762961)
Ah gotcha, have also been pretty impressed by pypyjs http://pypyjs.org/
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale
by Can_Not on Thursday April 05, 2018 @10:22AM
(#16765133)
> Erm... PSA: Rust isn't the only language that is compiling to WASM.
How many other languages are you expecting that most people really want to use but don't require a multi-megabyte VM?
Erm... PSA: Rust isn't the only language that is compiling to WASM.
I'm glad for Rust developers (How exciting is for them to be able to target WASM), but what is really exciting is to have alternatives; even more exciting if they have nothing to do with javascript.