* The payload of WASM makes it a difficult choice if serving mobile or regions with poor internet and you want a good first impression. * Server side needing a

* The payload of WASM makes it a difficult choice if serving mobile or regions with poor internet and you want a good first impression. * Server side needing a constant socket for everything presents it's own limitations. * It has hot reloading, but it pales in comparison to the JS experience at best and in my own experience has a lot of edge cases leading to full rebuilds. * C# tooling is fantastic; Razor however I've found to be slow and well behind the experience of popular JS libraries. * When you do need JS interop (e.g. browser API's) the experience is, IMO, awful. I feel Blazor's niche is internal, simple LOB apps and I can understand the appeal if you don't already know JS or have some serious regulatory requirements around vendors and need to avoid NPM. Personally, I find the DX and quality of the end product in svelte kit trump the code sharing of Blazor.