[sheepscreek]

In my limited experience, Blazor significantly simplifies front-end development, particularly in larger and more intricate projects. This is partly due to the maturity of .NET tooling and ecosystem, which makes it easy to manage projects at different scales of complexity.

[whoknowsidont]

"It works on my machine" is not simplifying front-end development. Please just stick with React, Hotwire, HTMX, literally anything else.

[sheepscreek]

I’m not sure what you’re referring to. Blazor, along with Razor pages, was developed to simplify front-end development in dotnet. It’s essentially the React of the C# world, enabling the embedding of both C# and HTML into Razor pages, both on the client and server sides.

Its most impressive feature, however, is LiveView, which is akin to server-side rendering. It’s more sophisticated than that. It does a diff on the state changes and only the diffed DOM node states are transmitted over the network, resulting in lightning-fast performance. In other words, if a value changes from <p>5</p> to <p>10</p>, only the 10 gets sent from the server (along with sufficient information to locate the correct location of the replacement).

[whoknowsidont]

Blazor is not robust. It is not ready for production websites.

Teams using Blazor are often not equipped to understand the stack and the intricacies of how it actually works under the hood, and therefore do not monitor for issues. And worse, when they become aware of these issues, they can do nothing to fix them (well, you technically can, most Blazor teams are not those teams).

>It’s essentially the React of the C# world,

No it is not even close to similar.

If you are using Blazor on a website today I bet you a very, very large amount of money your users are consistently running into issues they cannot recover from.

I know how Blazor works. A lot more than I care to.

If you are actively using Blazor today that's a huge fuck you to both your end-users and anyone being forced to interact with the application.