I can think of a few, starting with lack of fragmentation given Blazor's now the "premier" Web Application framework for .NET which has the full focus and devel

I can think of a few, starting with lack of fragmentation given Blazor's now the "premier" Web Application framework for .NET which has the full focus and developer resources of Microsoft, millions of .NET Developers and 3rd Party Component Developers. Low platform churn, i.e. Blazor has essentially kept the same development model for 5 years, uses the same MS Build/.NET SDK and Framework libraries that are actively supported by Microsoft. Whilst the JS/FX landscape see's frequent fragmentation, new incompatible major versions, new module loaders, new build tools, 100's of deps which are often abandoned/incompatible after upgrades, etc. Blazor SSR App's gives you SPA-like responsiveness to traditional SSR Apps by default, i.e. without needing to manage decoupled client routing, complex state, npm deps, build tools, large JS blobs, etc. Blazor makes it very easy to create encapsulated reusable components, which already sees a large number of 3rd Party component vendors available for it. The .NET Platform overall is very performant, works flawlessly cross-platform, C# is a very IDE-friendly statically typed language with great tooling e.g. JetBrains Rider is one of the best IDE's available for any language and works cross-platform.