4 ms·
This looks cool, even though I have never used .NET. Rust seems like something that a lot of people are using to compile into web assembly. It would be fascinat
by xrd 8y ago
This looks cool, even though I have never used .NET. Rust seems like something that a lot of people are using to compile into web assembly. It would be fascinating to see what alternatives there are here to those two and how they all compare. Go?
- k__ 8y agoI'm especially interested in the size of C#, Java and Go solutions that compile to WASM.
- mattferderer 8y agoThey're going to be large for a while. In time they'll shrink down to something more reasonable.
- pjmlp 8y agoSpecially since both support linkers and future WebAssembly improvements will reduce the runtime requirements.
- epse 8y agoIt sends a wasm build of the entire CLR and the same executables you can run natively, so it's gonna be big.
- untog 8y agoIIRC, Rust is often chosen because you don't have to embed a garbage collector with your code. That's not the case with Go (or C#)
- pjmlp 8y agoWebAssembly roadmap plans to add GC support, so that is only an interim issue.
- k__ 8y agoWhile I had the impression that GC support means the will expose the JavaScript engine's GC to be used by other languages and I don't know if it would work for all, is the GC really such a big chunk of these runtimes?
- oaiey 8y ago.NET has the concept of pluggable GC since last CoreCLR release. I highly suspect that other runtimes will have the same. I also have my doubts but more regards performance of a shared WebAssembly GC in regards to different runtimes.