.NET vs Django: What are the differences?
Both .Net and Django offer code-first ORM abstraction, large communities of support, examples of use in large organizations, and open source or community support for developers. The .NET framework is open source with C# completely being an open sourced language. The new ASP.net MVC is excellent and supports modern standards. With an ability to write complete HTML in it and libraries like jQuery, AngularJS, Backbone.js, Twitter Bootstrap and more. Django is a robust and accessible framework for python users. Developers can quickly start developing web applications with a highly customizable admin panel and authentication out of the box. With top-notch documentation available from the community, there is help available each step of the way. Secure and scalable to build applications.
What is Django?
What is .NET?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Django?
- Open source374
- Mvc214
- Elegant172
Why do developers choose .NET?
- Stable code233
- Microsoft118
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Django?
What are the cons of using .NET?
- C#2
Sign up to add, upvote and see more consMake informed product decisions
What companies use .NET?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Django?
What tools integrate with .NET?
Sign up to get full access to all the tool integrationsMake informed product decisions
I first found .NET in 2003 when I first began learning to create software. Every year since then, I've watched as .NET matured into something great, and now we have .NET Core! At Contessa Health, we use .NET Core for a mixture of things including fine-grained and coarse-grained web services, worker processes for long running tasks, and for our Azure Functions that serve as a replacement for distributing our base class libraries. As a startup, we are constantly evaluating technologies to make sure we stay fresh, and we keep coming back to .NET Core because of its ecosystem, maturity of the tooling, and for its ability to help us iterate and move quickly. Take all of that and combine it with the Kubernetes ecosystem, and we have an easy way to orchestrate and compose power service offerings that meet the needs of our customers. It cannot be said enough that Microsoft’s commitment to open source has yielded incredible benefits for small companies such as ourselves. Our voices are heard, and we get to help make .NET Core better, which in turn helps everyone else.
I've used .NET for many years, but only in recent years, after Microsoft introduced .NET Core, I've found a new love and excitement for the technology again. The main driver for us using .NET Core is not that it is cross platform compatible, open source or blazingly fast (which it is!), but the fact that we can use (what we consider) the best programming languages (mainly F# and C#) to carry out our jobs without sacrificing the other benefits.
Today we run most of our web infrastructure on .NET Core in Docker containers, deployed into a Kubernetes cluster which spans across multiple time zones in the Google Cloud and we couldn't be happier. Due to the portability of the .NET Core platform we are even able to develop many new services as serverless functions with F# which has become an absolute game changer.
Our focus is on mobile. I use .NET because most of my work involves Xamarin. We haven't had a need for .NET Core lately since Xamarin covers the iOS, Android bases. .NET Core seems best suited to larger organizations who need to port and migrate between Windows, Linux, and macOS. Seems incredibly useful, particularly the Windows/Linux crossover. But for us, Mono takes care of that already in Xamarin.
.NETMicrosoft has done an incredible job of keeping the .NET Framework powerful and stable. It is well designed and keeps getting more robust with each release. It isn't the most popular technology in this space, but I think a good case can be made to use .NET in many new projects.
DjangoDjango takes the hassle out of building an enterprise web application using Python.
- admin app for administration
- ORM for deploying against different database vendors
- social auth package for authentication with enterprise IdP
- guardian package for authorization
DjangoOur backend was written in Django. We took advantage of the ready-to-go admin interface as a go-to solution for the client to be able to authorize his users, as well as other functionality, while most of the work was done through the Django Rest Framework.
DjangoHands down the best Python web framework I've used. Very easy to extend and add apps and go from 0 to full project quickly and painlessly. I built a fully authenticated project with a single endpoint in less than 30 minutes.
.NETAs we started on Windows Phone we use C# and .NET for most of our apps and sites. Being a small team of 2, using .NET enables us to work on each part of the service without having to switch to different languages.
Django정말 편리하고 많은것을 알아서 제공해 주는 프레임워크 이다. 책의 예제만 진행해서 많이 써보지는 못했지만, 쉽게 쉽게 웹을 개발 할 수 있는 점이 매력적 이다. 게다가 orm 이 기본으로 내장 되어 있고 db 도 sqlite 가 기본으로 되어있어. 그냥 django 만 설치하면 바로 웹개발이 가능하다.
.NETI use .NET alongside with C# since my university studies, and I really enjoy it. Especially .NET Core, which is the best thing that happened to Microsoft since... ever.
Djangodjango는 저의 무기입니다.
django 이외에 flask로 간단한 restful api를 만들면서 느낀점은 framework 보다 언어가 중요하다는것을 알았고 django가 얼마나 큰 framework인지 알게되었습니다.
저는 signal 사용을 좋아합니다.
.NETServer side development language and frameworks: ASP.Net MVC 4, Asp.Net WebApi 2, Razor View engine, Moq, Entity Frameworks, etc.
.NETTwinCore creates modern web and cloud applications based on .NET TwinCore supports legacy .NET applications