ASP.NET Core vs React

Overview

React

Stacks182.6K

Followers147.0K

Votes4.1K

GitHub Stars240.3K

Forks49.7K

ASP.NET Core

Stacks11.0K

Followers2.7K

Votes1.6K

ASP.NET Core vs React: What are the differences?

Introduction: ASP.NET Core and React are two popular technologies used in web development. ASP.NET Core is a cross-platform, open-source framework for building web applications, while React is a JavaScript library for building user interfaces. While both technologies have their own strengths and purposes, there are key differences between them.

Language and platform: ASP.NET Core uses C# as its primary language and can be used to develop web applications on Windows, macOS, and Linux. On the other hand, React is based on JavaScript and can be used for developing user interfaces in web applications.
Server-side vs client-side rendering: ASP.NET Core supports server-side rendering, where the HTML is generated on the server and sent to the client browser. This can help with initial page load times and improve SEO. React, on the other hand, is primarily used for client-side rendering, where the HTML is generated on the client side using JavaScript. This allows for more dynamic and interactive user interfaces.
Tooling and ecosystem: ASP.NET Core comes with a comprehensive set of tools and frameworks, such as Visual Studio and Entity Framework, which provide a rich development experience. It also has a large ecosystem of libraries and packages available for different purposes. React has its own set of tools, such as Create React App and React Developer Tools, and a vibrant ecosystem with numerous libraries and packages specifically tailored for building user interfaces with React.
Learning curve: ASP.NET Core, being a full-featured framework, has a steeper learning curve compared to React. It requires understanding concepts like server-side programming, routing, and database access. React, on the other hand, focuses solely on the user interface and has a simpler abstraction model, making it easier for developers to learn and get started with.
Component-based vs MVC architecture: ASP.NET Core follows the Model-View-Controller (MVC) architectural pattern, where the application is divided into models, views, and controllers. React, on the other hand, uses a component-based architecture, where the application is built by combining reusable components. This allows for better code organization, reusability, and maintainability in React applications.
Performance and scalability: ASP.NET Core, being a server-side framework, has the advantage of running on the server, which can handle heavy processing and database interactions. This can result in better performance and scalability for certain types of applications. React, on the other hand, focuses on the client-side rendering, which offloads some of the processing to the client's browser, resulting in a more responsive user interface.

In summary, ASP.NET Core and React have key differences in terms of language and platform, server-side vs client-side rendering, tooling and ecosystem, learning curve, architecture, and performance and scalability. Understanding these differences can help developers choose the right technology for their web development needs.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on React, ASP.NET Core

Cyrus

Aug 15, 2019

Needs adviceon

Vue.js

React

I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

884k views884k

Comments

Cyrus

Aug 15, 2019

Needs advice

Simple datepickers are cumbersome. For such a simple data input, I feel like it takes far too much effort. Ideally, the native input[type="date"] would just work like it does on FF and Chrome, but Safari and Edge don't handle it properly. So I'm left either having a diverging experience based on the browser or I need to choose a library to implement a datepicker since users aren't good at inputing formatted strings.

For React alone there are tons of examples to use https://reactjsexample.com/tag/date/. And then of course there's the bootstrap datepicker (https://bootstrap-datepicker.readthedocs.io/en/latest/), jQueryUI calendar picker, https://github.com/flatpickr/flatpickr, and many more.

How do you recommend going about handling date and time inputs? And then there's always moment.js, but I've observed some users getting stuck when presented with a blank text field. I'm curious to hear what's worked well for people...

401k views401k

Comments

Damiano

Oct 27, 2019

Decided

Preact offers an API which is extremely similar to React's for less than 10% of its size (and createElement is renamed to h, which makes the overall bundle a lot smaller). Although it is less compatible with other libraries than the latter (and its ecosystem is nowhere as developed), this is generally not a problem as Preact exposes the preact/compat API, which can be used as an alias both for React and ReactDOM and allows for the use of libraries which would otherwise just be compatible with React.

25.6k views25.6k

Comments

Detailed Comparison

React	ASP.NET Core
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.	A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.
Declarative; Component-based; Learn once, write anywhere	-
Statistics
GitHub Stars 240.3K	GitHub Stars -
GitHub Forks 49.7K	GitHub Forks -
Stacks 182.6K	Stacks 11.0K
Followers 147.0K	Followers 2.7K
Votes 4.1K	Votes 1.6K
Pros & Cons
Pros 837 Components 674 Virtual dom 579 Performance 509 Simplicity 442 Composable Cons 41 Requires discipline to keep architecture organized 30 No predefined way to structure your app 29 Need to be familiar with lots of third party packages 13 JSX 10 Not enterprise friendly	Pros 143 C# 118 Performance 96 Open source 90 NuGet 84 Easy to learn and use Cons 5 Great Doc 3 Fast 2 Professionally written Nuget Packages, vs IMPORT junk 2 Clean 1 Long polling is difficult to implement
Integrations
No integrations available	Linux Docker macOS NGINX .NET Apache HTTP Server Windows Microsoft IIS .NET Core

What are some alternatives to React, ASP.NET Core?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

jQuery

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Related Comparisons

ASP.NET Core vs React: What are the differences?

Language and platform: ASP.NET Core uses C# as its primary language and can be used to develop web applications on Windows, macOS, and Linux. On the other hand, React is based on JavaScript and can be used for developing user interfaces in web applications.
Server-side vs client-side rendering: ASP.NET Core supports server-side rendering, where the HTML is generated on the server and sent to the client browser. This can help with initial page load times and improve SEO. React, on the other hand, is primarily used for client-side rendering, where the HTML is generated on the client side using JavaScript. This allows for more dynamic and interactive user interfaces.
Tooling and ecosystem: ASP.NET Core comes with a comprehensive set of tools and frameworks, such as Visual Studio and Entity Framework, which provide a rich development experience. It also has a large ecosystem of libraries and packages available for different purposes. React has its own set of tools, such as Create React App and React Developer Tools, and a vibrant ecosystem with numerous libraries and packages specifically tailored for building user interfaces with React.
Learning curve: ASP.NET Core, being a full-featured framework, has a steeper learning curve compared to React. It requires understanding concepts like server-side programming, routing, and database access. React, on the other hand, focuses solely on the user interface and has a simpler abstraction model, making it easier for developers to learn and get started with.
Component-based vs MVC architecture: ASP.NET Core follows the Model-View-Controller (MVC) architectural pattern, where the application is divided into models, views, and controllers. React, on the other hand, uses a component-based architecture, where the application is built by combining reusable components. This allows for better code organization, reusability, and maintainability in React applications.
Performance and scalability: ASP.NET Core, being a server-side framework, has the advantage of running on the server, which can handle heavy processing and database interactions. This can result in better performance and scalability for certain types of applications. React, on the other hand, focuses on the client-side rendering, which offloads some of the processing to the client's browser, resulting in a more responsive user interface.

ASP.NET Core vs React

Overview