4 ms·
It's unlikely to be a money problem (nor Microsoft cares that much about .NET to do so). WASM also makes it pretty much irrelevant. Current Mono-WASM solution w
by neonsunset 2y ago
It's unlikely to be a money problem (nor Microsoft cares that much about .NET to do so). WASM also makes it pretty much irrelevant. Current Mono-WASM solution works decently enough but is far from perfect. Hopefully NativeAOT-LLVM project gets released in the next couple of versions as it improves the performance and bundle size massively.
- BrendanEich 2y agoRight, wasm is the low energy path. IMO you should think about this problem-space of the Web as an evolutionary system, with costs weighting all the paths through a graph from current state to future state. MS throwing money at C# native VM (the CLR? Silverlight's DLR? lol) as second VM in browsers, with separate GCs bridged, incurring the write barrier overhead that I cited already? In all browsers, not just the ones MS can bribe to do the considerable work? No. C# compiled to WebAssembly? One GC, all good, perhaps some warm evolution is on order, but it is an incremental cost.