Blazor is based on a build of .NET (CLR + BCL) for WASM - though it is highly optimized and unused code is aggressively removed from the WASM bundles it still means your users will need to download (at least) 6MB of WASM while your SPA loads - which makes Angular look anorexic in comparison.

...which basically restricts Blazor's use to corporate LAN environments, kiosk applications, and (maybe) PWAs - but it's otherwise completely unsuitable for use on the wider public Internet.

...but we know it'll end-up being used on the public web eventually anyway because developer time is worth more than the end user UX.

Which may look huge but not big problem for enterprise web apps. First load may be slow but it is then cached.

This is just the adage software is a gas. linkedin.com now takes 5.1mb; users are simply becoming accustomed to larger web based applications.

The .Net team has made pretty significant strides in minimizing the bundle size and I would expect that to continue. It’s now also possible to combine pre-rendering and streaming with web assembly to improve the loading experience.

You're talking specifically about Blazor client-side framework which is designed for e.g. games or drawing apps where 6mb of downloads isn't particularly onerous.

The far more common use-case is Blazor server-side which doesn't have this huge download overhead and works like server-side rendering in e.g. React, the download is approximately 150kb.

>it still means your users will need to download (at least) 6MB of WASM

Isn't it like 1 second of scrolling through Instagram?

Angular has really improved in this area, the addition of standalone components mean your initial payload can be very small indeed, and then just lazy load the rest as/if you need it.