Front technology: which one is better option for new application razor-vs-angular

Question

0.00/5 (No votes)

See more:

My team is planning to convert our older application to new Enterprise level web application.

So, we are doing some research into the latest web frameworks. For the backend we have selected.Net Core web API with the SQL Server as Database. This layer will remain disconnected with the UI layer, as we are planning to use the same Web API for a mobile app as well.

We wanted to get some expert opinions on the "new" Razor vs. Angular.

What I have tried:

We are particularly more concerned with performance, along with the this also consider Development efforts as we all are new with both the technology.

How does Core 2.0 Razor hold up to client-side rendering frameworks?

Is there any performance difference between both?

Which one is more mature in terms of front development?

Which technology has larger developer community?

Are we able to host both of it, on Linux/Unix server?

Thanks in advance!

Posted 8-Apr-19 19:32pm

User 14187550

Updated 9-Apr-19 1:37am

v2

Add a Solution

Comments

F-ES Sitecore 9-Apr-19 7:42am

Razor and Angular are not comparable technologies. Razor is a server-side scripting engine that generates html, angular is a client-side MVCesque framework.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

MadMyche · Answer 1 · 2019-04-09T01:38:00

Angular is the more mature platform, has a lot larger community, and Google is littered with samples to follow. The downside is it is continuously evolving and you may have to alter your code in the future if methods use become deprecated.

Blazor looks like it will out perform most JS framerworks, but has nowhere near the community or samples to work with. While it is a new technology, it's underpinnings are pretty set as the code will be ASP.NET. When the front-end component updates it will mostly be done via the mono.js file or through the SignalR communication to the backend; the ASP.NET code targeting should remain the same.

Either can be implemented on most server platforms as long as the requisite components are installed.