Why We Choose Blazor over React and Vue: Matt Jones

[@9sparkfuls]

Thoughtful. Thanks.

[@zimcoder]

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

[@FlorianZevedei]

Interesting talk. Im Dev in with Blazor since late 2021 (.Net 6), used it in all main projects and not regretting it. Sure there where some lets call it "undocumented behaviour" which wasnt clear why it happend. But its Microsoft, so your getting used to it and get it to work. Glad since then many updates have found their way into this technology and still today using it. 26:57 That "first load thingy", happens only with Blazor Webassembly. Not with Blazor Server. Probably the use case forced them to use WebAssembly. With Blazor servers its pretty quick.

[@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.

[@melliflousbufo]

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

[@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.

[@caseyspaulding]

Nice!

[@LOFIBOT-bp6hm]

the problem with Blazor is SignalR, blazor without persistence connection (websockets) will be amazing

[@abhayprince]

Try Blazor WASM and Static SSR

[@randypenajimenez3893]

Unless that is an app with a massive quantity of users Blaozr ssr is more than good.

[@nan5715]

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

[@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

[@nan5715]

Silverlight

[@AnthonyPaulT]

So stupid choosing blazer. So dumb. Wasting money

[@lukevincent4397]

You clearly don't code in C# LOL.

[@portlyoldman]

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.