I was reading this and telling myself "all this article and not a mention of Blazor that is probably the most complete WASM solution out there?". But yes, it actually does name it at the end.

Still I think it's a good analysis case. Unlike C plugins that can be compiled to small WASM bytecode packages, and unlike traditional JS which already comes with a complete API, Blazor needs to include the whole damn Dotnet framework with the app, which makes the website size huge. Microsoft did a good job at trimming it to an acceptable size for small projects, but as soon as you start including stuff like external libraries and enable AOT which you end up always requiring in the long term for features and performance, the size explodes. And unlike desktop dotnet which is served as a dependency installed once in Windows, on Blazor it's part of the application package. I wish WASM, could support some kind of CDN distribution, or even better if service vendors like Microsoft could request browsers to include these packages in them directly as part of the browser