Why We Choose Blazor over React and Vue: Matt Jones

Presented at ThunderPlains 2023, hosted by Techlahoma
Special thanks to:
Simiancraft, our Exclusive Recording Sponsor simiancraft.com/
Emcees: Shanda Biggs, Aaron Krauss, Jacqueline Sims, and Erich Keil
Editors: Geoffrey Harden and Patricia Salas
Learn more about Techlahoma at techlahoma.org
You can support our non-profit through any of the following:
- Volunteering help-wanted.techlahoma.org
- Donations donate.techlahoma.org
- Subscribing to our Twitch channel for free if you have an Amazon Prime account: / techlahoma

[@zimcoder]

You may need to give this talk again in light of the .NET 8 and the massive improvement in Blazor.

[@melliflousbufo]

Really helpful - thanks. Exactly the kind of questions I'm asking myself.

[@generic2345]

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.

[@caseyspaulding]

Nice!

[@nan5715]

Who the hell is writing a lot of jquery these days. This is funny

[@Ash-vu5vo]

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.

[@nan5715]

Silverlight

[@nan5715]

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.

[@obinnaokafor6252]

Terrible performance

[@AnthonyPaulT]

So stupid choosing blazer. So dumb. Wasting money