> for someone who develops web application backends and larger distributed systems Blazor: It's Microsoft's way of doing in-browser C#. It can do quick-and-dir

> for someone who develops web application backends and larger distributed systems Blazor: It's Microsoft's way of doing in-browser C#. It can do quick-and-dirty server-side HTML, and professional-grade, in-browser WASM. Why is this useful "for someone who develops web application backends"? The nice thing about server-side Blazor is that you can make a management console, or otherwise port ops scripts, into a self-service page. Because you can choose to render on the server, you don't have to write an API, serialize your response, ect. You can do a SQL-ish query (with LINQ and Entity Framework) in the middle of HTML. (Granted, for production-grade pages Blazor can run in the browser as WASM and use industrial-strength APIs.)