3 ms·
And with existing .Net, C, Go, Rust, Lua, Zig, Crystal, D, Elixir, also Java, JavaScript, Kotlin, Lisp, Nim, Pascal, Perl, PHP, Python, R, Ruby code (non-exhaus
by reyqn 3y ago
And with existing .Net, C, Go, Rust, Lua, Zig, Crystal, D, Elixir, also Java, JavaScript, Kotlin, Lisp, Nim, Pascal, Perl, PHP, Python, R, Ruby code (non-exhaustive list).
That's a lot of flexibility
- pjmlp 3y agoJust like the CLR in 2001!
- deleted 3y ago[deleted]
- doodlesdev 3y agoSo here's the thing, CLR is still here (now called CoreCLR as of the move to .NET Core), how does it differ technically from WASM/WASI, and why aren't we using it instead? I should note I haven't spent much time studying either of them.
- pjmlp 3y agoMostly because Micro$oft shenanigans, or the fear thereof. As if the VCs baking up all those WASM products are doing it from the warmth of their hearts.
- garganzol 3y agoThey will do all the mistakes that have to be done. WASM GC is one of them.
- pjmlp 3y agoProbably, then again if it was only for C and C++ style workloads, even one more reason to stick to the past. https://en.wikipedia.org/wiki/Architecture_Neutral_Distribution_Format https://en.wikipedia.org/wiki/Architecture_Neutral_Distribut... Just one example out of many others, for C and C++ based workloads.