Need advice about which tool to choose?Ask the StackShare community!

.NET

5.5K
4.3K
+ 1
1.7K
Next.js

2.7K
2.6K
+ 1
241
Add tool

.NET vs Next.js: What are the differences?

What is .NET? A free, cross-platform, open source developer platform for building many different types of applications. .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.

What is Next.js? *A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications.

.NET and Next.js can be primarily classified as "Frameworks (Full Stack)" tools.

Some of the features offered by .NET are:

  • Multiple languages: You can write .NET apps in C#, F#, or Visual Basic.
  • Cross Platform: Whether you're working in C#, F#, or Visual Basic, your code will run natively on any compatible OS.
  • Consistent API & Libraries: To extend functionality, Microsoft and others maintain a healthy package ecosystem built on .NET Standard.

On the other hand, Next.js provides the following key features:

  • Zero setup. Use the filesystem as an API
  • Only JavaScript. Everything is a function
  • Automatic server rendering and code splitting

"Tight integration with visual studio" is the primary reason why developers consider .NET over the competitors, whereas "Automatic server rendering and code splitting" was stated as the key factor in picking Next.js.

.NET and Next.js are both open source tools. It seems that Next.js with 38.7K GitHub stars and 4.69K forks on GitHub has more adoption than .NET with 11.1K GitHub stars and 2.4K GitHub forks.

According to the StackShare community, .NET has a broader approval, being mentioned in 1566 company stacks & 239 developers stacks; compared to Next.js, which is listed in 82 company stacks and 69 developer stacks.

Advice on .NET and Next.js
Needs advice
on
.NET Core.NET Core.NET.NET
and
C#C#

I have to write an application for a Windows Server that either runs on a scheduled task or can run on a Windows server and triggered by a webhook. What other .NET project types or methods within a project can I do this with?

I know I could probably host an API on IIS on the Windows server and do it that way, but all my APIs are in Azure App service, and this has to integrate with the Windows desktop application.

See more
Replies (2)
Recommends
Azure FunctionsAzure Functions

What you mean integrate on "all my APIs are in Azure App service and this has to integrate with Windows desktop application.". Try to explain a little bit what's your requirements.

If you want to Read/Write a SQL DB on premises, you can use a Azure Gateway without deploy anything in your server, another choice with SQL Server is to move the DB to Azure (if supported). You can use the triggers on Azure Functions to write/read something on Azure Storage, from your Server you can read the storage and perform some tasks. As you can see there are multiple choice without writing much code on premises, try to clarify your requirements.

See more
Recommends
.NET Core.NET CoreC#C#

It all depends on your use case. You mentioning "scheduled task" appears you want to use a Worker Service

If you want to trigger your actions you can host a webapi, too.

Bottomline: Both use cases suffice your needs so your course depends on where you want to "control" your app ( set delay, maybe sometimes start the action manually ). WorkerService -> Config file on the host Api -> Configure from client

See more
Decisions about .NET and Next.js

We choose Next.js for our React framework because it's very minimal and has a very organized file structure. Also, it offers key features like zero setups, automatic server rendering and code splitting, typescript support. Our app requires some loading time to process the video, server-side rendering will allow our website to display faster than client-side rending.

See more
Ing. Alvaro Rodríguez Scelza
Software Systems Engineer at Ripio · | 11 upvotes · 144K views

I was considering focusing on learning RoR and looking for a work that uses those techs.

After some investigation, I decided to stay with C# .NET:

  • It is more requested on job positions (7 to 1 in my personal searches average).

  • It's been around for longer.

  • it has better documentation and community.

  • One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.

  • Rail's front end support is starting to waver.

  • C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.

  • Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.

I would avise to stick to rails when building small projects, and switching to C# for more long term ones.

Opinions are welcome!

See more
Fronted Rent

We’re a new startup so we need to be able to deliver quick changes as we find our product market fit. We’ve also got to ensure that we’re moving money safely, and keeping perfect records. The technologies we’ve chosen mix mature but well maintained frameworks like Django, with modern web-first and api-first front ends like GraphQL, NextJS, and Chakra. We use a little Golang sparingly in our backend to ensure that when we interact with financial services, we do so with statically compiled, strongly typed, and strictly limited and reviewed code.

You can read all about it in our linked blog post.

See more
Lucas Litton
Founder & CEO at Macombey · | 13 upvotes · 256.2K views

Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

See more
Ing. Alvaro Rodríguez Scelza
Software Systems Engineer at Ripio · | 8 upvotes · 211.2K views

Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.

Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.

See more

Hey guys,

My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of .NET
Pros of Next.js
  • 262
    Tight integration with visual studio
  • 250
    Stable code
  • 180
    Great community
  • 171
    Reliable and strongly typed server side language.
  • 132
    Microsoft
  • 110
    Fantastic documentation
  • 83
    Great 3rd party libraries
  • 72
    Speedy
  • 65
    Great azure integration
  • 58
    Great support
  • 26
    Linq
  • 26
    Highly productive
  • 24
    High Performance
  • 24
    C#
  • 23
    Great programming languages (C#, VB)
  • 20
    Open source
  • 14
    Clean markup with razor
  • 14
    Powerful Web application framework (ASP.NET MVC)
  • 13
    Powerful ORM (EntityFramework)
  • 11
    Fast
  • 9
    Visual studio + Resharper = <3
  • 9
    Dependency injection
  • 9
    Constantly improving to keep up with new trends
  • 7
    TFS
  • 6
    Security
  • 6
    Job opportunities
  • 6
    High-Performance
  • 6
    Integrated and Reliable
  • 5
    Light-weight
  • 5
    Huge ecosystem and communities
  • 4
    Variations
  • 4
    Lovely
  • 3
    Scaffolding
  • 3
    Entity framework
  • 3
    Support and SImplicity
  • 3
    {get; set;}
  • 3
    Asynchrony
  • 3
    Concurrent
  • 3
    Useful IoC
  • 2
    Default Debuging tools
  • 1
    Nuget package manager
  • 1
    Blazor
  • 35
    Automatic server rendering and code splitting
  • 29
    Built with React
  • 26
    Easy setup
  • 19
    Zero setup
  • 19
    Universal JavaScript
  • 17
    TypeScript
  • 13
    Static site generator
  • 9
    Just JavaScript
  • 9
    Incremental static regeneration
  • 9
    Simple deployment
  • 8
    Frictionless development
  • 7
    Filesystem as an API
  • 7
    Isomorphic React applications
  • 7
    Testing
  • 6
    Has many examples and integrations
  • 6
    Well Documented
  • 6
    Everything is a function
  • 5
    Not nuxt
  • 3
    Not vue
  • 1
    File based routing + hooks built in

Sign up to add or upvote prosMake informed product decisions

Cons of .NET
Cons of Next.js
  • 9
    Too expensive to deploy and maintain
  • 9
    C#
  • 7
    Microsoft itself
  • 6
    Microsoft dependable systems
  • 3
    Hard learning curve
  • 1
    Not have a full fledged visual studio for linux
  • 1
    Tight integration with visual studio
  • 7
    Not Vue
  • 6
    Structure is weak compared to Angular(2+)
  • 2
    Is no Angular
  • 2
    Not flutter
  • 1
    Not Angular 2

Sign up to add or upvote consMake informed product decisions

What is .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.

What is Next.js?

Next.js is a minimalistic framework for server-rendered React applications.

Need advice about which tool to choose?Ask the StackShare community!

What companies use .NET?
What companies use Next.js?
See which teams inside your own company are using .NET or Next.js.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with .NET?
What tools integrate with Next.js?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to .NET and Next.js?
ASP.NET
.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
Java
Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!
Python
Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
PHP
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.
JavaScript
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
See all alternatives