3 ms·
They're nowhere near the same. WASM is based on linear memory and has no concepts of objects and methods. CIL bytecode as used by .NET has a full runtime which
by Jasper_ 8y ago
They're nowhere near the same. WASM is based on linear memory and has no concepts of objects and methods. CIL bytecode as used by .NET has a full runtime which has objects, methods and GC. Even with the GC proposal, as currently spec'd, it would not be able to handle .NET's object model.
The only similarity, really, is that they're both binary formats.
- pjmlp 8y agoThat doesn't stop Microsoft to keep improving Blazor.
- Jasper_ 8y agoBlazor is a .NET interpreter written in C++ that's compiled to WebAssembly. You can think of it as being comparable to Duktape or another JavaScript interpreter being compiled to WebAssembly and running some JavaScript code. It won't JIT anything.
- pjmlp 8y agoNo it isn't JITing, but you missed the part they are improving CoreRT to use AOT compilation to WebAssembly instead. Just like Unity is already doing with their Lightweight Components and HPC#.