.NET Blazor 的现状如何？
1 分•作者: hliyan•9 个月前
最近在使用 .NET Razor 页面，此前十年一直在用 React + Node，我开始欣赏这种主要由服务器端渲染的代码的简洁性，它使用原生强类型、编译型语言，并拥有丰富的标准库。但我听说 Blazor 比较新，也更好。考虑到它似乎是一个用 WebAssembly (!) 构建的客户端 .NET 运行时，再加上微软在前端技术方面的历史，我搜索了 HN 上过去的相关讨论，找到了 2021 年的这条评论：
<p>https://news.ycombinator.com/item?id=26885807</p>
>> 微软在这些前端工作上投入的精力真是令人难以置信。
> 在 winforms、silverlight、wpf、webforms 和 WinUI 之后，我不想看到精力，我希望看到他们能专注超过 5 分钟。微软唯一一个有长期支持的稳定 UI 技术是 25 年前推出的 Win32。
> 我预测 Blazor 将被悄悄放弃（他们实际上不会承认，至少 5 年），就像其他技术一样，几年后你将被迫重写你的软件。
作者的 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?