Django
A batteries-included Python web framework for building database-backed web applications.
Loved for its batteries-included ORM, admin and authentication123 and for shipping CRUD web apps quickly with little upkeep.456 The most common complaint is that it is slow and memory-hungry,789 with weak async support also noted.1011
Why people recommend it
Batteries included · 3
Commenters value how much comes built in, sparing them from rebuilding fragile boilerplate.
“I keep going back to the batteries-included Django simply for the ORM, the admin backend and authentication packages.”
“when things come with Django, there's no need to maintain or worry about subtle yet crucial bugs.”
Show 1 more
“something as batteries-included and expressive like Rails or Django”
Admin interface · 3
The auto-generated admin is a main reason people keep choosing Django and use it as a backstop UI.
“The Django admin is a core reason why I still choose Django over other solutions.”
“Django is the main thing I miss from python.”
Show 1 more
“Django is hands down one of my favorite frameworks ever created”
ORM and migrations · 3
Some use Django models and migrations even in Go, Java or Rust stacks.
“I still use Django for models and migration.”
“Django is hands down one of my favorite frameworks ever created”
Show 1 more
“For us, it has absolutely been a major benefit.”
Fast to build · 3
Simple Django apps are seen as quicker to build and cheaper to maintain than SPAs.
“if it’s something you could do with e.g. a simple Django app you’ll not only be done faster but will spend an order of magnitude less time on maintenance”
“90% of the SPAs I use could be Django/Rails/Flask apps with no noticeable difference”
Show 1 more
“some non-standard requirements were really difficult to implement or get around”
Readable conventions · 3
Its conventions make code quick to review, including code written by LLMs.
“Django code is pretty easy to review quickly. LLMs are good at writing it.”
“You'll have to pry Django from my cold, dead hands.”
Show 1 more
“wow would it be a waste of tokens and your projects surface area would be dwarfed by the complexity of just building your own alternative to Django”
Stable releases · 3
Users praise small, manageable changes between versions and good documentation.
“I love how Django just keeps slowly improving at every release.”
“Django is pretty nice, the changes between versions are small and can be managed by a human.”
Show 1 more
“Django was really well-written, and had great documentation, and I could get going with it really quickly.”
Caveats and dissent
Performance · 3
Several commenters call Django slow and wasteful of memory.
“Django is slow, and the filters and custom shit to hit db on the template makes it slower.”
“I find python django wastes too much resources, just look at memory usage.”
Show 1 more
“It still selects all fields by default.”
Async support · 2
Async is seen as a weak spot, pushing some users to Go or Celery.
“I'd love Django, if they had a better async story”
“However, I love Django and Python in general.”
Size and bloat · 2
Some find the framework and its docs too large to keep in their heads.
“I'm currently migrating a project from Django to Go because Django is too large.”
“Django code is pretty easy to review quickly. LLMs are good at writing it.”
Typing and structure · 2
Long-time users cite painful typing, a leaky ORM and bloated models.
“I've been building in Django for a long time and I love the framework”
“looking at you Django, don't be so dynamic your brains fall out”
Maintenance burden · 1
Upgrading older projects with many dependencies can take a lot of time.
Non-standard needs · 2
Unusual requirements can be hard to implement, and some features like Content Types are best avoided.
“some non-standard requirements were really difficult to implement or get around”
“As someone who's used Django since 0.97 and loves it”
Often compared with
Who recommends it in their own words
Threads where it came up
- Some more things about Django I've been enjoying 6 mentions
- What I love about Django 5 mentions
- Django: what’s new in 6.0 4 mentions
- Django 6 3 mentions
- What About Rails? 2 mentions
- Topcoat: The full full-stack framework for Rust 2 mentions
Data: django.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 42
“most any Python programmer can reliably churn out a Django app as a Microservice and be fairly sure it won't be that hard to make”
“You'll have to pry Django from my cold, dead hands.”
“I used Django for my most-recent project, and don't regret that decision a bit.”
“Run a django web application I wrote for my own use.”
“Python, Django, FastAPI, PostgreSQL, Celery”
“when things come with Django, there's no need to maintain or worry about subtle yet crucial bugs.”
“something as batteries-included and expressive like Rails or Django”
“I figured I'd use my go-to, Django”
“Django is slow, and the filters and custom shit to hit db on the template makes it slower.”
“Then Python/Django for 10 years.”
“a Django-based JS-free forum”
“And Django is amazing.”
“Django's capabilities meant such things as multi-user login pages, access controls and remote monitoring were very easy.”
“I keep going back to the batteries-included Django simply for the ORM, the admin backend and authentication packages.”
“As many of these projects, data is kind of central, I use Django.”
“It still selects all fields by default.”
“As someone who's used Django since 0.97 and loves it”
“I'd love Django, if they had a better async story”
“Django is hands down one of my favorite frameworks ever created”
“some non-standard requirements were really difficult to implement or get around”
“I love Django's approach to configs: your config is just a plain old Python file with some constants.”
“I'm currently migrating a project from Django to Go because Django is too large.”
“automatic migrations terrifies me.”
“I used to agree with this more strongly but over time decided the Django model was actually more effective”
“For us, it has absolutely been a major benefit.”
“I still use Django for models and migration.”
“I find python django wastes too much resources, just look at memory usage.”
“Django is the main thing I miss from python.”
“Django, Laravel, and Rails are very neat.”
“building a Django app that is all about the data model”
“those run on a separate Django backend”
“For web apps, Rails, Django, Laravel.”
“Thanks to template engines (for me it's Django's, but Jinja or others are grand too)”
“if it’s something you could do with e.g. a simple Django app you’ll not only be done faster but will spend an order of magnitude less time on maintenance”
“90% of the SPAs I use could be Django/Rails/Flask apps with no noticeable difference”
“I ask ChatGPT to ingest the logs into a Django web application”
“Django has been my daily driver since 2018 — I've only worked with Django-native startups.”
“I still have a lot of good memories with Django.”
“I appreciate the value of Django too”
“Django code is pretty easy to review quickly. LLMs are good at writing it.”
“The Django admin is a core reason why I still choose Django over other solutions.”
“However, I love Django and Python in general.”