3 ms·

Also, even when WebAssembly gets proper threading, .NET/Mono still uses a "suspend the world" GC mode which will still halt your execution. Nobody is poo-poo'i

by pknopf 8y ago

Also, even when WebAssembly gets proper threading, .NET/Mono still uses a "suspend the world" GC mode which will still halt your execution. Nobody is poo-poo'ing anything. It is what it is. .NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical. I expect Rust to lead the way here.

GiorgioG 8y ago
> .NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical. I guess I don't understand what kind of 'high-scale applications where performance is critical' wouldn't be suitable for .NET but instead better suited to a systems programming language like Rust. If the bottleneck becomes the single-threaded JS interop, then what difference does it make which WASM language/runtime you choose as long as it's at least as fast as JS?
- pknopf 8y ago
  Rust has no GC, .NET has a GC. Rust will be delivered with no runtime (minimal deployed size), Blazor will need the entire mono runtime and BCL.
  - GiorgioG 8y ago
    It won't require everything to be downloaded - https://www.mono-project.com/news/2018/01/16/mono-static-webassembly-compilation/ https://www.mono-project.com/news/2018/01/16/mono-static-web... Will it ever be as small as a systems language like Rust or C? No - never. But the productivity gains that C# & the .NET framework provide are a worthwhile tradeoff for 99% applications. The .NET team is actively working to optimize the payload to a manageable size. You haven't specified what evidence you're basing this statement on: > ".NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical." Because Javascript is a good fit? Facebook sends down 500k+ of JS and how many of their billion+ customers complain about it?

3 ms·

Also, even when WebAssembly gets proper threading, .NET/Mono still uses a "suspend the world" GC mode which will still halt your execution. Nobody is poo-poo'i

by pknopf 8y ago

GiorgioG 8y ago
> .NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical. I guess I don't understand what kind of 'high-scale applications where performance is critical' wouldn't be suitable for .NET but instead better suited to a systems programming language like Rust. If the bottleneck becomes the single-threaded JS interop, then what difference does it make which WASM language/runtime you choose as long as it's at least as fast as JS?
- pknopf 8y ago
  Rust has no GC, .NET has a GC. Rust will be delivered with no runtime (minimal deployed size), Blazor will need the entire mono runtime and BCL.
  - GiorgioG 8y ago
    It won't require everything to be downloaded - https://www.mono-project.com/news/2018/01/16/mono-static-webassembly-compilation/ https://www.mono-project.com/news/2018/01/16/mono-static-web... Will it ever be as small as a systems language like Rust or C? No - never. But the productivity gains that C# & the .NET framework provide are a worthwhile tradeoff for 99% applications. The .NET team is actively working to optimize the payload to a manageable size. You haven't specified what evidence you're basing this statement on: > ".NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical." Because Javascript is a good fit? Facebook sends down 500k+ of JS and how many of their billion+ customers complain about it?