.NET Blazor的现状如何？
最近，我开始使用 .NET Razor 页面，结束了十年的 React + Node 开发，我逐渐欣赏到使用一种本地强类型、编译语言和丰富标准库的服务器渲染代码的简单性。但我听说 Blazor 更新且更好。不过，考虑到它似乎是一个基于 WebAssembly 的客户端 .NET 运行时，以及微软在前端技术方面的历史，我在 HN 上搜索了过去的讨论，发现了这条来自 2021 年的评论：
https://news.ycombinator.com/item?id=26885807
>> 微软在这些前端项目上投入的精力真是令人难以置信。
> 在 WinForms、Silverlight、WPF、WebForms 和 WinUI 之后，我不想要精力，我想看到他们专注超过 5 分钟。微软唯一一个有长期支持的稳定 UI 技术是 25 年前推出的 Win32。
> 我预测 Blazor 会被悄悄放弃（他们实际上不会承认这一点，可能要等 5 年），就像其他技术一样，你将被迫在几年内重写你的软件。
作者的五年预测结果如何？Blazor 是在增长，还是在衰退？
查看原文
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:<p>https://news.ycombinator.com/item?id=26885807<p>>> The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible.<p>> 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.<p>> 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.<p>How has the author's 5 year prediction panned out? Is Blazor growing, or languishing?