I'm a member of a team of C# developers and we're considering Blazor for modernizing a large enterprise ASP.NET MVC app.<p>In the light of the recent overwhelming events in the .NET space, we'd be interested in opinions about what the future of Blazor could be, should Microsoft decide to stop maintaining it.<p>I've created a Twitter poll (upd: the link is in the comments below), you could see the current results if you cast a vote:<p>- Blazor is here to stay<p>- An active community fork<p>- A "life support" scenario<p>- Use another framework now<p>I'll update this post with the final results when the poll ends.<p>Thanks!
Im curious what you anticipate the longevity of your app to be? Lots of things are possible. My last company has a fairly critical Angular 1 app from early 2010s. Guess what, it works! It’s ~9 years later and going strong. It has a big enough team to keep the lights on, and only now is it probably reaching a serious inflection point.<p>But IMO if I had to do it again and cared about longevity I’d avoid a framework. I would probably also avoid JavaScript, and maybe even putting much complexity in the web tier. Instead I’d probably find a way to get my business logic in a CLI and make any clients fairly disposable.
The final results:<p>- Blazor is here to stay: 42.3%<p>- An active community fork: 12.4%<p>- A "life support" scenario: 13.8%<p>- Use another framework now: 31.5%<p><a href="https://twitter.com/noseratio/status/1452598283063357443?s=20" rel="nofollow">https://twitter.com/noseratio/status/1452598283063357443?s=2...</a>