zlacker

There's nothing magic about it. Web Forms was a great innovation and brought the WinForms model to the web. It was more productive than anything else at the time and directly influenced MVC patterns (which asp.net itself went towards) and component-based UI.

Blazor is the next evolution in client-side and offers an alternative to building component UI with C# running through WebAssembly instead of Javascript. Again it's much more productive and lets backend teams reuse much of the same code, similar to JS/node projects today.

Blazor's server-side runtime is a optional model where all the component logic can run on the server and be delivered over a SignalR connection to further increase productivity and efficiency where it makes sense (highly constrained devices, local intranet apps, etc. There's even experimental projects to bring Blazor for mobile apps.