So Reason through BuckleScript compiles to JS, right? That in theory should make it possible to use WebAssembly from the compiled JS. Not sure how far along native interoperability is, it probably entails compiling Reason/Ocaml to it directly, and not just targeting JS as an output.
I'm not sure you could compare Reason and Rust directly though, unless you're talking in the general sense of two languages that can compile to native code.
ReasonML is here for a while but seem not very welcomed by the frontend community, yet
I might be mistaken and I know they are not the same thing but I feel like TypeScript is taking Reason shot at "mainstreamability". JS developers seem to be mostly interested in typing to help them with large code bases and TS gives them those without increasing the cognitived load too much. TS also allows them to incrementally improve the code without having to rewrite it. We'll live to see what happens in all of those communities of developers.
How would you compare them together, how do you see their places in the future ?
Currently Rust has the better tooling around WebAssembly but once WebAssembly will be "finished" in the browser and the system interface will be completed, I'm sure which language is used to target wasm will not matter much if at all (and that's a great thing!). I'm really excited about the future of WebAssembly on and beyond the web.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So Reason through BuckleScript compiles to JS, right? That in theory should make it possible to use WebAssembly from the compiled JS. Not sure how far along native interoperability is, it probably entails compiling Reason/Ocaml to it directly, and not just targeting JS as an output.
I'm not sure you could compare Reason and Rust directly though, unless you're talking in the general sense of two languages that can compile to native code.
I might be mistaken and I know they are not the same thing but I feel like TypeScript is taking Reason shot at "mainstreamability". JS developers seem to be mostly interested in typing to help them with large code bases and TS gives them those without increasing the cognitived load too much. TS also allows them to incrementally improve the code without having to rewrite it. We'll live to see what happens in all of those communities of developers.
Currently Rust has the better tooling around WebAssembly but once WebAssembly will be "finished" in the browser and the system interface will be completed, I'm sure which language is used to target wasm will not matter much if at all (and that's a great thing!). I'm really excited about the future of WebAssembly on and beyond the web.