Blazor vs. TypeScript/Angular

Question

Hi;

This is for a brand new project. All new code. So we can use anything. It's a web app so the server side will be .NET Core ASP.NET. But question for the client side.

What are the advantages/disadvantages of Blazor vs. TypeScript/Angular? I'm very strong in both C# and TypeScript/JavaScript but I prefer C# so Blazor sounds enticing to me.

And does Blazor have a future at Microsoft? I think back to the people (not me) that went all in on web forms or silverlight. I don't want to go there.

Update: This is for an app that is sort-of like a very simplistic SalesForce. So multiple different pages, each of which provides different functionality. And most pages are interactive, as opposed to just displaying information.

thanks - dave

Answer 1

You should definitely go with blazor, It has future. So many big companies uses SPA and now they are moving to WebAssembly PWA.
There are so many third party components that can work with blazor. Also its very easy to create your own.

I convert my almost all projects into blazor.

Answer 2

there is no way to predict the long term support of either platform. Blazor has more support now, than I would have guessed. Who knows what browser technology will be popular in the coming years.

Depending on your app design there may be performance differences. Blazor uses a virtual dom (similar to react), Angular an incremental dom. Typescript is not truly type safe while Blazor is. angular can directly access the dom, Blazor uses js interop.

I still pick react/javascipt over Blazor because there is much less boiler plate code, and code is often simpler. Also there is a larger pool of 3rd party components. I would pick Blazor over angular anytime (but that is just me).

also, is it a single page web app or a website? for a website I'd probably recommend razor pages and javascript.