Is Blazor Better than Angular?

[@GavinLon]

Hi everyone. I discovered a small oversight on my part. At around the 00:02:25 mark - I say "The main reason for JavaScript's existence is to provide static typing to JavaScript.". I, of course meant "The main reason for TypeScript's existence...." -Sorry about that. :)

[@MarkoMijuskovic]

For me personally Blazor is the future...

[@GavinLon]

I think Blazor is going to go from strength to strength!

[@dirkschannel5817]

Another great video. I fully agree that there is no winner from a technical standpoint. From a business point of view I would choose .NET & Blazor. Maybe I’m biased, the bigger company it’s more likely to find .NET or Java.

[@GavinLon]

Great comment! Absolutely - I really love .NET because of its robustness, versatility and sophistication. If I was to build a full-stack enterprise application, I could only choose .NET. Now that Blazor has new enhancements like for e.g. allowing for mixed render modes for components in one project - I would definitely choose Blazor as the front-end technology.

[@granddesignsstudio]

Blazer and DI is now a no brainer for me.

[@vktop2]

Great video, what can you comment about the security and performance between Blazor and Angular?

[@GavinLon]

For a sophisticated solution regarding security for both Angular and Blazor I would recommend using an implementation based on the OAuth 2.0 protocol, such as OpenID Connect (OIDC). In terms of performance the answer is not straight forward. Both technologies are highly performant - you'll get great client side performance using Blazor WebAssembly but you'll also get great performance using Angular. Blazor server can be prone to latency due to its reliance on a signal-r connection, although in my experience with Blazor Server - it performs consistently well. New features like SSR and streaming rendering shipped with .NET 8, have certainly enhanced the performance capabilities of Blazor. Blazor is continuously evolving and excellent enhancements are being added every year - so the performance for Blazor applications is likely to continue to improve moving forward :)

[@razakalsharafy4708]

Thanks for the great video. Humm ... most comparison I've seen ends up with the same conclusion 🤔🤔🤔 means promoting the new MS technology that still not measure enough yet (as usual). I still remember Borland's (turbo C/Pascal/Basic) and dBase III/Clipper ... but MS dominate even Lotus 123/WordPerfect and so on. Key to learn: Marketing is the key to success. Well, I don't spend much time learning newer IT tech over building App and invested heavily on C# . Glad to know Blazor will help avoid learning React/Angular or any other platform.

[@GavinLon]

You are very welcome! Thanks for your great comment, I really enjoyed reading it! Blazor really is great! I do like the JavaScript SPA frameworks but for someone already familiar with C# and .NET, and has not yet ventured into the SPA domain (as it were) - I would certainly recommend learning the Blazor SPA framework :)

[@OggVorbis69]

Turbo pascal was ide and compiler on a stiffy. Fastest compiler at the time. Its,worth adding that the same guy that gave you type script an c sharp was behind that too. How we ended up using Java script from all things is sad.

[@alexandrverenchuc7524]

Thanks for the great video. You have a small error in Video Time Indexes, instead of Angular there is Next.js for some reason

[@GavinLon]

Oh thanks! I'll correct that now :)

[@hassanOnYoutube]

Angular community & UI library is so large. To me, Angular is a winner in long run.

[@GavinLon]

Angular is great. I hope Blazor's community will grow larger in time :)

[@zimcoder]

short answer, yes it is!

[@paulgehrman]

Angular's steep learning curve suggests design flaws to me, no matter how powerful it is once you master it. React is friendlier, but I think Blazor is better than both now, and will continue to improve. Of course, developers and their religions...

[@GavinLon]

I definitely found React far more friendlier than Angular. Blazor is both powerful and friendly in my opinion. They're all great technologies, but yes as you alluded to in your comment, the benefits of Microsoft investment in Blazor should ensure that Blazor keeps getting better! :)

[@krasserTerror]

Signals (which were introduced in Angular 17) are changing Angular from the ground up. Everything has gotten a lot easier since their introduction.

[@mesutdemirci7933]

Thanks for the great video.

[@GavinLon]

You are very welcome! Thank you for your positive feedback! :)

[@iR0CKt]

I dont know how dotnet will behave in some years. But with angular 8 my project is completely unusable with today's npm packages. To fix it i would have to do a lot of work. An old react project of similar age at least compiled and started with the latest react version etc when i tested it a few weeks ago. One component was broken, still way better than the angular experience i had. Just for that i do dislike all node solutions as they do break easily.. The upgrade of my latest dotnet blazor wasm app on the other hand from dotnet 7 to 8 was almost done in two clicks. The app worked without changing anything code wise. It's been only one version upgrade tho so that experience may be worse if upgrading from dotnet 7 to 12 if it would be the latest version.

[@GavinLon]

I think Microsoft, without a doubt, create the best software products! 👍You can't go wrong with Blazor - also far easier to debug!

[@hammeedabdo.82]

Thanks Gavin! Which framework will be in the first place during the next two years? In my personal opinion, either React or Next.js will be in the first position in the coming years.

[@GavinLon]

I like Next.js, one of the main reasons being that you can write full-stack applications using one technology. This is also one of the reasons why I love Blazor! :)

[@botyironcastle]

I think neither of these will ever replace react (unfortunately)

[@GavinLon]

I do love React! :)

[@mjdev-i1p]

As a Senior Fullstack DEV for over 15 years now I can tell everyone with absolute confidence and passion ... C# is not meant to be used for the web ... it's just bad honestly

[@GavinLon]

Okay, thank you, I appreciate your opinion :) Could you please elaborate as to why you think C# should not be used for the web?

[@OggVorbis69]

Thanks for the great video. Turbo pascal was ide and compiler on a stiffy. Fastest compiler at the time. Its,worth adding that the same guy that gave you type script an c sharp was behind that too. How we ended up using Java script from all things is sad. Blazer just wins on fundamentals alone.one language for both ends is amazing plus. Tooling can help only do much.

[@GavinLon]

Great comment - yes Anders Hejlsberg is awesome!

[@OggVorbis69]

From business perspective blazor wins

[@GavinLon]

I totally agree!

[@kristiadhy]

What do you mean by from business perspective? Is it because there will be much of Blazor jobs in the future?