[throwawaymaths]

I thought blazor failed because people didn't like websites that take minutes to load up all the websites assets. I'm not sure why, it could be:

- Technical issue with blazor performance or blazor makes perf regressions hard to fix

- blazor technical framework encourages programming style that is bad for perf

- blazor or blazor ecosystem attracts programmers that can't deal with perf issues

[josephg]

As I understand it, blazor really needs WasmGC in order to have good performance and small bundle sizes. Otherwise, blazor is forced to ship a GC inside the wasm bundle - and that adds a lot of weight. And it also makes it more complex to share C# objects with javascript.

WasmGC is supported in all browsers + nodejs now, but its still pretty new. Safari only started shipping it in December last year. I'm not sure if wasmgc is the default build for blazor, or what the status is on it.

Blazor should be able to be good, small and fast. (Maybe even smaller than rust web frameworks.) But I don't know if we're there yet.

[chris_pie]

.NET doesn't use WasmGC because Microsoft found it too different from how .NET's GC works. Which is quite unfortunate

[josephg]

Oh what a pity. Anywhere I can read more about that?

[chris_pie]

I can't find the actual decision, but there was some discussion here: https://github.com/WebAssembly/gc/issues/77 Microsoft later in 2023 said that that discussion "is the current state we are in. We will keep eye on wasm GC in the future."

edit: found a more concrete statement https://github.com/dotnet/runtime/issues/94420

[lylejantzi3rd]

Doesn't Blazor include the entire .net core runtime? Or has that changed?

[throwawaymaths]

Then explanations 2&3?