|
|
|
|
|
by hellwd
1975 days ago
|
|
I would suggest you not to choose Blazor. It's not that Blazor is bad or that I have something against, but you don't want to limit yourself when it comes to finding a Blazor developer. You will hardly find a frontend developer who is focusing on Blazor.
Today are React, Angular, Vue or similar frameworks the best way to go, especially for a startup where you need flexibility. Keep using .NET for a backend, provide a nice API and implement frontend using already mentioned frameworks. |
|
Finding developers with Blazor focus/experience, seems to have two sides. One is .net developers really want to work on Blazor, and other is that not many have experience. By "choose boring technology" standards, these are both red flags.
However, I wonder if it is more work to implement Vue than Blazor considering my existing stack and that much of app is already developed. Razor pages use the same syntax as Blazor.