ReactJS vs Blazor

Alright. I know what you are saying. This type of comparison should be reserved for … Read more ReactJS vs Blazor

Alright. I know what you are saying. This type of comparison should be reserved for Medium posts, and here (on StackOverflow) it will only lead to a holy war. Definable not what I am trying to do. Let me set the parameters for this questions.

I have been a long time React developer. In my current environment, I deal a lot with MS products (mainly SQL Server). Over time, I have found it easier to support this type of architecture using .NET Core (for a small team perspective), and it seems like .NET Core can be much more standards based (because it’s Microsoft and it a non-interpreted language). As I am moving forward with a few new projects, I have concerns using something like Blazor. It is fairly new, there is not as much community packages (when compared to React), and I see pretty much everyone and their dog is using React (including Microsoft).

Now, let me get this out of the way. I have attempted to use .NET Core on the backend and React + TS on the front end, but I very quickly ran into what I would call “types hell” (having types for WebAPI on the backend, but no interfaces or types in TS). It was a nightmare to manage, and I really don’t want to have to go this direction again.

Can anyone give me any reason why I should or should not be worried to use Blazor in a production application? Better yet, can someone give me a good reason why I should/should not use React on the front end?

If I were not using SQL for my DB, does that change anything? Let the discussion begin!

Source: JavaSript – Stack Overflow



Leave a Reply

Your email address will not be published. Required fields are marked *