Thanks for this. This was valuable insight. I am in the same process of deciding between React with .Net or Blazor. The new changes coming to Blazor looks promising.
This was like hoping to see a comparison of two brands of chocolate, only to find discussion around the wrapping, branding, stores they are available in, and who tends to eat them, with no comparison of the actual chocolate itself. While I agree with your final decision, you missed the biggest difference: design patterns. Also fyi, if you’re already in .Net land, absolutely pointless to even consider a different runtime. If you do, you clearly don’t value being DRY, monorepos, and static references enough. All in all, totally missed the mark here.
How about go full stack js like node and next.js and done one language and trust me the dev time will be same or better. You’re clearly more comfortable in net so excellent choice.
Thanks for your well researched, deep consideration of the available options . No, wait, that wasn’t you 😡 A shop that has C# developers and understands the .Net architecture inside out would need a very good reason to choose a JS or TS based SPA over Blazor. you are just being naive.
You may need to give this talk again in light of the .NET 8 and the massive improvement in Blazor.
Thanks for this. This was valuable insight. I am in the same process of deciding between React with .Net or Blazor. The new changes coming to Blazor looks promising.
Really helpful - thanks. Exactly the kind of questions I'm asking myself.
the problem with Blazor is SignalR, blazor without persistence connection (websockets) will be amazing
Try Blazor WASM and Static SSR
Unless that is an app with a massive quantity of users Blaozr ssr is more than good.
Nice!
This was like hoping to see a comparison of two brands of chocolate, only to find discussion around the wrapping, branding, stores they are available in, and who tends to eat them, with no comparison of the actual chocolate itself. While I agree with your final decision, you missed the biggest difference: design patterns.
Also fyi, if you’re already in .Net land, absolutely pointless to even consider a different runtime. If you do, you clearly don’t value being DRY, monorepos, and static references enough.
All in all, totally missed the mark here.
Who the hell is writing a lot of jquery these days. This is funny
How about go full stack js like node and next.js and done one language and trust me the dev time will be same or better. You’re clearly more comfortable in net so excellent choice.
Terrible performance
Silverlight
So stupid choosing blazer. So dumb. Wasting money
You clearly don't code in C# LOL.
Thanks for your well researched, deep consideration of the available options . No, wait, that wasn’t you 😡 A shop that has C# developers and understands the .Net architecture inside out would need a very good reason to choose a JS or TS based SPA over Blazor. you are just being naive.