Have not tried Blazor, but from what I read it, state management is leaning server side from ASP.net roots.
GREAT if security is needed in your biz casr (would not want local debug option in banking app...)
But for other things goes against "chunky, not chatty" mantra, while Internet hops are still the highest hurdle.
Of course you can create create "smart controls", but this will clash with MVVM mind set.

I prefer using client side cpu, SSD, cache and info and minimize calls back into the server for minute details.

Having 1 language front and back is good - from vfp over Javascript running on Node server of Blazor with C# backend- unless you alreadyhave battletested code you can reuse, which trumps single language even if only architected with a bit of planning or thought of replacing layers.

my 0.000022€
thomas

>So I thought it would be an easy decision to make. Where Should I go next. Angular or React. I decided to go with React for a bunch of reasons.
>
>And now here comes Blazor. I never really heard about it in the last weeks. But recently that changed.
>
>Comments?
>
>Regards