from Hacker News

What is the state of .NET Blazor?

by hliyan on 8/25/25, 11:53 AM with 1 comments

Having recently started using .NET Razor pages after a decade of React + Node, I've come to admire the simplicity of mostly server-rendered code using a natively strongly typed, compiled language with a rich standard library. But I've been told that Blazor is newer and better. But considering that it seems to be a client-side .NET runtime built with WebAssembly(!) and Microsoft's history with front-end technologies, I did a search on past discussions on HN and found this comment from 2021:

https://news.ycombinator.com/item?id=26885807

>> The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible.

> After winforms, silverlight, wpf, webforms and WinUI I don't want energy, I want to see them focus for more than 5 minutes. The only stable UI tech from MS with any long term support has been Win32 that came out 25 years ago.

> I predict blazor will be quietly dropped (they won't actually admit it for 5 years), just like the others and you'll be forced to rewrite your software in a few years.

How has the author's 5 year prediction panned out? Is Blazor growing, or languishing?

  • by danroth27 on 8/25/25, 11:00 PM

    Blazor has come a long way since 2021 and is still going strong. Blazor Web Apps can now be rendered server-side, using either static or interactive server-side rendering, as well as client-side via WebAssembly. You can also host your Blazor components in native mobile and desktop apps using Blazor Hybrid. Because of this flexibility, Blazor is now the recommended .NET web UI framework in ASP.NET Core. It can handle traditional server-side rendering (like you could do with MVC or Razor Pages) as well as fully interactive scenarios that would otherwise require JavaScript.