[pjmlp]

Between all my main development stacks, .NET, Java and node, I have still no reason to adopt Blazor besides toy projects.

I really don't know how to make out of it.

It started by being .NET for WebAssembly, and then it took a life of its own, with the team pushing it everywhere there is a Webview, as if the GUI civil war going on Redmond wasn't already bad enough.

Since WebForms was a victim of the "Python 2 / Python 3" like reboot of the .NET ecosystem, at very least Blazor provides a similar development experience for those folks.

For the rest of us, used to clean MVC approaches, without allergy to JavaScript, mostly working in mixed FE/BE teams, Blazor is a solution looking for a problem, not worth the additional amount of complexity layers between browser and applications.

Web Forms and JSF have taught me not to go there again.