Django

“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”

“The framework acts as guardrails and the LLM has to make fewer choices, so less of the token budget goes on bikeshedding.”

“Django's capabilities meant such things as multi-user login pages, access controls and remote monitoring were very easy.”

“Django's orm does not support something as simple as specifying a database schema other than the default "public" one out of the box.”

“Django is the only thing I've used where I've vibe-coded an app, then looked at the code and not been appalled.”

“Django's docs are excellent, so strategically pointing an LLM to them in a prompt can often produce great results.”

“Django makes simple things easy and complex things hard. Django breaks the zen of Python with much 'magic'.”

“Yes, if you attempt to use Django like you'd use your typical Java, Swift, C#, or Objective-C framework, you're not going to have a good time.”

“Migration churn adds up over the years but overall it's nice and site-specific code is usually so small it fits very nice in LLM context”

“We could much more that back 15 years ago on very basic hardware, rendering templates and doing semi complex UIs.”

“django tracks the migrations that were run inside the database so they'd all see the same thing and act the same way.”

“Running your API in Rust/Go/etc and then doing the admin and migrations via Django is a hidden superpower.”

“Django apps are an anitipattern for large internal / single purpose products due to migration overhead as FKs cross application boundaries”

“If you deploy it reasonably well (workers, behind a caching reverse proxy etc) it's easy to operate in production even under duress.”

“I haven't seen anything which is so flexible with amazing DSLs while also making it easy to understand the magic behind it.”

“A mature Django app is also not a nice dev experience IMO, with tons of implicit behavior all over the place”

“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”

“For a broad range of requirements, running your DB directly and managing auth with Django or similar is easier.”

“if I do a search on AI and on google for what one web stack probably has the lowest overall total cost of ownership”

“I'm afraid of a system like Django where not calling `.save()` in the wrong place is down to discipline and understanding.”

“Django in particular is optimized for LLMs as it's based on Python and has a strong set of design patterns built over decades”

“The framework allows you to trust that things like authentication and a passable code organization are being correctly handled.”

“Django is in the category of battle-tested frameworks that are very boring and easy to get things done with.”

“Django is boring in a best possible way. Rather than spending six months setting up a bunch of microservices, you spend couple weeks on Django and ship a working product.”

“you can probably figure out some basic django to throw data in its ORM, or find libraries that do the work for you”

“Django is very good at having the autogenerated/default stuff be consistent with what you do if you want to write manually”

“It's so prevalent that Claude/Codex are very good at setting it up the right way, using tried and true patterns.”

“Django just starts you with a good convention that (mostly) prevents you from doing things that you’ll regret later”

“It's just the right amount of magic, and just the right amount of flexibility, and it's just such a joy to work with.”

“It was basically an admin interface, but with dozens of models and hundreds if not thousands of individual fields”

“Django is objectively the most productive "boring technology" I've ever worked with for developing web applications.”

“starting with a base like django then using vibe coding to build models and templates exactly how one wants”

“I would not say that about a framework like Django - though I would encourage people not to under-invest in understanding web fundamentals”

“put the Django architecture together on vacation, started putting things together today and it’s been a blast.”

“supported both Python 2 AND 3 before I even found out that Python 3 was going to have significant breaking changes”

“I found that everything makes sense and I was able to build a moderately complex site with user accounts within a reasonable time”

“I am an extremely satisfied django developer, and very very very rarely touch frontend. Django is A-M-A-Z-I-N-G.”

“still feels tremendously cozy to use. I've done some goofy things with it and it's always served me really well.”

“It's frustrating because we use all manner of hacks to work around this being part of the builtin story.”

“As soon as you hit something Django doesn't support, you're back to lego-ing a solution together except you now have to do it in a framework with a lot of magic and assumptions to work around.”