Built a few things with Blazor (largely internal tooling). Feels like a cross between Meteor, WebForms, and Phoenix LiveView. Fast and simple. - Server-side

Built a few things with Blazor (largely internal tooling). Feels like a cross between Meteor, WebForms, and Phoenix LiveView. Fast and simple. - Server-side rendering is great for internal apps, or public facing ones where interactivity is minimal and you enforce websocket support. Lost connections are still messy, but a single codebase (literally) makes life very simple. - Client-side rendering is great for internal apps, or public facing ones where users are fine with a reasonable-sized up-front traffic hit. Lost connections behave like with any other site, and you can still use shared code and libraries which work unchanged on client and server. I quite like the latter. A DotNet solution with a client C# project, a server C# project, and shared code projects, with the server running an API and the client consuming it using shared models works well and supports end-to-end debugging. I'm also looking forward to trying the DotNet 8 hybrid Blazor improvements. That said, when doing C# I still prefer either plain ASP.Net MVC or a separate client hitting an ASP.Net Web API (pretty much the perfect mix of scalable performance and productive development).