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.
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:
- Blazor is here to stay
- An active community fork
- A "life support" scenario
- Use another framework now
I'll update this post with the final results when the poll ends.
Thanks!
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.
It might as well happen with Blazor, if it's kept further maintained as a part of .NET normal release cycles for years to come, and won't be stripped out in some next major release.
- Blazor is here to stay: 42.3%
- An active community fork: 12.4%
- A "life support" scenario: 13.8%
- Use another framework now: 31.5%
https://twitter.com/noseratio/status/1452598283063357443?s=2...