8 ms·

Django 6

391 points by wilhelmklopp 11mo ago

echelon 11mo ago
Show of hands for backend web services development - Who uses Django, Rails, or similar full-featured frameworks? Who uses micro-frameworks like Flask? Who uses enterprise Java, Jetty, Dot Net, etc.? Who uses an entirely Javascript stack? Who uses a non-traditional language that has become more web-servicey, like Go, Rust, or Swift? Who uses something so wildly untraditional that it's barely mentioned? OkCupid using C++, etc.? Who uses an entirely custom framework (in any language)? Would really love to see a break down of who is using what, how people feel about their tech stack, etc.?
- justinator 11mo ago
  Perl, CGI.
  - echelon 11mo ago
    Love it! Which version of Perl are you using, and what type of service(s) are you maintaining? Is this older software, or do you use it for new projects too? Have you rolled any sort of framework yourself? What are your thoughts on Raku?
    - justinator 11mo ago
      I target 5.10.1 mostly. This is for a project I started in the late 90's. It uses CGI::Application, which is less a framework and more a method lookup table converter of queries (although I built a path info convertor on top of that). It's still maintained, although before Covid, it was my livelihood. About a quarter of a million lines of code, excluding the libraries I pull in. I'm mostly self-taught, they wouldn't even let me get a minor in Comp Sci, since I didn't have the math background (Needed Calculus, I completeled Algebra 2 in hs). Boneheaded Uni. Raku: Second-system effect poster boy. Sensationally dysfunctional community. I think Pugs is what was actually really incredible and Audrey is probably one of the most intelligent people in... the World? Up for contention, but top 10.
      - samtregar3 11mo ago
        [dead]
- yoavm 11mo ago
  I still have some very old Django projects that I'm maintaining for > 15 years. It's an absolute delight.
  - collinmanderson 11mo ago
    Yes. I'm still maintaining a Django site that I helped get live in 2007. I started learning Django in 2006.
- hecanjog 11mo ago
  This would make an interesting poll. I think that's possible here? Maybe with some karma threshold, I don't seem to be able to make one. We use flask and go at work. I've been micro-framework or roll-my-own-framework most of my career. Go is new for me though, and it's grown on me enough that it's what I prefer for new web-facing projects even for little personal things.
  - echelon 11mo ago
    What should the options be? Were the ones I suggested coarse grained enough to capture everyone, or should I/we re-group or add more?
- thewebguyd 11mo ago
  I"m almost entirely dotnet these days, with a smattering of Go here and there. I work in ops though, so I'm not building consumer-facing products but mostly IT glue code and internal tooling (mostly Go), dashboards, business report generators, gluing SaaS together, etc. (mostly dotnet/C#).
- tcdent 11mo ago
  I started using Django before the official 1.0 release and used it almost exclusively for years on web projects. Lately I prefer to mix my own tooling and a couple major packages in for backends (FastAPI, SQLAchemy) that are still heavily inspired by patterns I picked up while using Django. I end up with a little more boilerplate, but I also end up with a little more stylistic flexibility.
  - BeetleB 11mo ago
    > I started using Django before the official 1.0 release Indeed. I'm still using the 0.97beta. It's perfectly good for production use! </obscure joke>
- wg0 11mo ago
  - Have written Rails and Django both - Have written SPAs (React/Svelte) - Have written Go based services Each has their on pros and cons.
- bossyTeacher 11mo ago
  Fable (just for the fun of it) and the new one dot net one file web services that resemble flask
- alberth 11mo ago
  One proxy might be to look at the upvote counts for each of their respective latest release HN posts. Eg, this post has ~50 (though only posted an hour ago) Rails 8 had ~550 https://news.ycombinator.com/item?id=41766515 https://news.ycombinator.com/item?id=41766515
  - echelon 11mo ago
    Rails might not get a lot of new articles about it, and the chatter might have died down, but I think a lot of people still use it.
  - canadiantim 11mo ago
    It’s amazing how much rails devs feel the need to denigrate Django, feels like an inferiority complex.
- rabbitvictor 11mo ago
  At work, it is mainly Kotlin and Go webservices with some Rust for very specific use cases
- debugnik 11mo ago
  In what sense is Go not a traditional language for web services? They're almost the only thing it's good at, and it's been doing them for 13 years.
  - monooso 11mo ago
    I agree that Go is a good choice for web services. I disagree that it's the only thing Go is good at. DevOps tooling and CLI tools immediately spring to mind.
    - debugnik 11mo ago
      Fair, CLI tools is why I said almost, but there's much more competition there. I wouldn't consider devops tools to be its own category though.
- aerhardt 11mo ago
  As fully-featured as possible, because as much as I like building stuff, I don’t give a shit about coding stuff that has been figured out since the 90’s. Another question is whether semantics and operations get bloated or affect development speed in a framework but I don’t think it’s the case with the Django.
- rick1290 11mo ago
  Would love to see this. Django just makes life 1000x easier. Can architect an app with data models, api, openapi, etc. within an hour.
- zelphirkalt 11mo ago
  In a company that uses a traditional web framework like Django to actually build the frontend and backend, not just as only for implementing the APIs, I would even consider doing parts of frontend work again, making everything responsive and so on. That's what I do for a not-yet-startup project.
- codr7 11mo ago
  I've done several custom frameworks for solo projects in Java & Go, all based on server generated content, inspired by Seaside but more RESTy. Also used Flask and similar libraries for back ends. Did one project in Rails, which was a pretty bad experience in comparison, and killed any motivation to look into Django. Also did plenty of Spring in Java professionally, unfortunately.
- kstrauser 11mo ago
  Flask is my go-to, but I've had great fun with Rust recently. Django is the best thing in the world for writing Django apps. (No, I'm not trying to be funny there. If what you're doing looks like something Django would solve, it's fantastic.) But most of the things I do aren't Django apps, and ones you get off its happy path, you can be in for a world of hurt. Oh, you use SQLAlchemy everywhere else, and you'd like to use it in your Django app so that you can have one set of models and re-use the service logic you've built? Hah, too bad! Or you need your REST API output to look a very specific way? Have fun with that! Your auth model doesn't look just like Django's? Hope your LLM is good at smoothing that over! The good side is that it's an opinionated framework that does a lot of research on your behalf and makes some great choices. The bad side is that you better agree with its opinions or you're in for a bad time.
nadermx 11mo ago
Django's batteries included setup makes it a no brainer for almost any project big or small. Kudos to the team and contributers
ianberdin 11mo ago
Thanks to Django. I got into the webdev world so easily. Curious, how come Django started to make major versions instead of 1.*? Can be the decreasing in popularity the reason to make Something to change it?
- yoavm 11mo ago
  It didn't - https://www.djangoproject.com/download/#supported-versions https://www.djangoproject.com/download/#supported-versions
  - ianberdin 11mo ago
    Oh, looks more transparent.
  - Muromec 11mo ago
    It's amazing, that django docs look and feel exactly the same the did in 0.9x. Damn kids with their JS bullshit have to change the whole site between v1 and v2 and then again when v3 happens. Links rot, API index is hidden and instead of text you get a dump of TS interfaces with zero comments. /rant
sparklingmango 11mo ago
Whenever I use Django, I enjoy it. Simple as.
ChrisArchitect 11mo ago
Blog post yesterday: https://www.djangoproject.com/weblog/2025/dec/03/django-60-released/ https://www.djangoproject.com/weblog/2025/dec/03/django-60-r... (https://news.ycombinator.com/item?id=46136516 https://news.ycombinator.com/item?id=46136516)
wg0 11mo ago
Can someone remind me how we ended up in the SPA era and why exactly? Was it about not seeing the loading spinner? Or there were more reasons to it?
- jorl17 11mo ago
  - Strict team separation (frontend versus backend) - Moving all state-managament out of the backend and onto the frontend, in a supposedly easier to manage system - Page refreshes are indeed jarring to users and more prone to leading to sudden context losses - Desktop applications did not behave like web apps: they are "SPA"s in their own sense, without jarring refreshes or code that gets "yanked" out of execution. Since the OS has been increasingly abstracted under the browser, and the average computer user has moved more and more towards web apps[1], it stands to reason that the behavior of web apps should become more like that of desktop apps (i.e. "SPA"s)[2] (Not saying I agree with these, merely pointing them out) [1] These things are not entirely independent. It can be argued that the same powers that be (big corps) that pushed SPAs onto users are also pushing the "browser as OS" concept. [2] I know you can get desktop-like behavior from non-SPAs, but it is definitely not as easy to do it or at least to _learn it_ now. My actual opinion: I think it's a little bit of everything, with a big part of it coming from the fact that the web was the easiest way to build something that you could share with people effortlessly. Sharing desktop apps wasn't particularly easy (different targets, java was never truly run everywhere, etc.), but to share a webapp app you just put it online very quickly and have someone else point their browser to a URL -- often all they'll do is click a link! And in general it is definitely easier to build an SPA (from the frontender's perspective) than something else. This creates a chain: If I can create and share easily -> I am motivated to do things easily -> I learn the specific technology that is easiest -> the market is flooded with people who know this technology better than everything else -> the market must now hire from this pool to get the cheapest workers (or those who cost less to acquire due to quicker hiring processes) -> new devs know that they need to learn this technology to get hired -> the cycle continues So, TL;DR: Much lower barrier to entry + quick feedback loops P.S (and on topic): I am an extremely satisfied django developer, and very very very rarely touch frontend. Django is A-M-A-Z-I-N-G.
  - 11mo ago
sroerick 11mo ago
Django was my first big freelance project, and still feels tremendously cozy to use. I've done some goofy things with it and it's always served me really well. Thank you Django
alex1138 11mo ago
[flagged]
willahmad 11mo ago
Django is awesome, but I wish there was an easy way to use modern web frameworks with it. A lot of times it's either through Nextjs/Nuxtjs + Django as an API or complex bundling process which requires a file where you register bundle versions/manifests then another build process which embeds them into template both are so complex
- stevex 11mo ago
  Django + AlpineJS + HTMX is pretty nice.
  - FartinMowler 11mo ago
    Especially with template partials now in the core of Django 6.
  - HiPhish 11mo ago
    That's just for the HTML content though. What if you want to add some non-trivial Javascript or generated CSS? Or maybe you want to integrate a frontend tool like Storybook[0] even if your HTML is rendered server-side? Maybe add some tests for your frontend code? There is much more between raw hand-rolled HTML/CSS/JS and a full-blown SPA. At my day job we use Django with HTMX and Alpine, but we also generate the custom CSS from Pico[1] and use JinjaX[2] to define server-side components which we then render in Storybook. We use Vue as our bundler to compile the JS and CSS as well as to run Storybook. The project has to live in both the Python ecosystem and the Node.js ecosystem. Even with just HTMX and Alpine you might want to compile a custom version of those with certain plugins, or you might want to load them as libraries in your own scripts. [0] https://storybook.js.org/ https://storybook.js.org/ [1] https://picocss.com/ https://picocss.com/ [2] https://jinjax.scaletti.dev/ https://jinjax.scaletti.dev/
    - michaelyin 11mo ago
      [dead]
- mushufasa 11mo ago
stevex 11mo ago
One thing Django has going for it is that the "batteries included" nature of it is perfect for AI code generation. You can get a working site with the usual featuers (admin panel, logins, forgot reset/password flow, etc) with minimal code thanks to the richness of the ecosystem, and because of the minimal code it's relatively easy for the AI to keep iterating on it since it's small enough to be understandable in context.
- throwawaymaths 11mo ago
  why would you need batteries included? the ai can code most integrations (from scratch, if you want, so if you need something slightly off the beaten path it's easy
  - jorl17 11mo ago
    I think the logic can be applied to humans as well as AI: Sure, the AI _can_ code integrations, but it now has to maintain them, and might be tempted to modify them when it doesn't need to (leaky abstractions), adding cognitive load (in LLM parlance: "context pollution") and leading to worse results. Batteries-included = AI and humans write less code, get more "headspace"/"free context" to focus on what "really matters". As a very very heavy LLM user, I also notice that projects tend to be much easier for LLMs (and humans alike) to work on when they use opinionated well-established frameworks. Nonetheless, I'm positive in a couple of years we'll have found a way for LLMs to be equally good, if not better, with other frameworks. I think we'll find mechanisms to have LLMs learn libraries and projects on the fly much better. I can imagine crazy scenarios where LLMs train smaller LLMs on project parts or libraries so they don't get context pollution but also don't need a full-retraining (or incredibly pricey inference). I can also think of a system in line with Anthropic's view of skills, where LLMs very intelligently switch their knowledge on or off. The technology isn't there yet, but we're moving FAST! Love this era!!
    - codr7 11mo ago
      Maybe if they could learn how to switch their intelligence on, that would help more?
personjerry 11mo ago
Do you guys find Django includes enough batteries? Why or why not? I find myself using Cookiecutter Django [^1] more often than not, better auth, a bunch of boilerplate configs, S3 and email setups if you want, and other stuff rather than have to jiggle with "Django infra" myself [^1]: https://github.com/cookiecutter/cookiecutter-django https://github.com/cookiecutter/cookiecutter-django
gnulinux996 11mo ago
What is the Java equivalent of Django? I really love django and everything around it, but I would also like to write a webapp in Java. Getting django + rest_framework up and running and actually be productive takes me max 10 minutes, trying to do the same with spring boot I am a week in and I had to open the jakarta specs to understand the magic.
- frikk 11mo ago
  How about this? https://github.com/dropwizard/dropwizard https://github.com/dropwizard/dropwizard
- atomicnumber3 11mo ago
  Java honestly just does not have this. By the time java collectively decided that being able to spend your time writing your actual product instead of fucking with config shit forever, the age of the monolithic SSR templated backend app were gone. So now most modern things like helidon focus on being microservicey like go, or they have very soft template rendering offerings and don't really do batteries included. I feel your pain, I myself am working on a react frontend + spring boot backend and fiddling with it to integrate with spring session, security, etc properly was a HUGE pain because neither world knows anything at all about each other. If I did it from scratch I'd just "rails new myapp" and be done already.
  - haolez 11mo ago
    Isn't there Thymeleaf that alleviates that?
    - atomicnumber3 11mo ago
      Forgive me, but thyme leaf is soft compared to ERB and jinja.
- frio 11mo ago
  I'm not sure why people aren't saying Spring Boot, but Spring Boot. Yeah it has heaps of other batteries included, and it doesn't have a built-in admin, but it gives you pretty decent stuff out of the box
blorenz 11mo ago
Django powers my SaaS. I use it mainly as a data backend with its ORM, admin, and incorporate Strawberry graphql into it for the data exchange to my frontends. I wish it was better with async, though.
- patrick91 11mo ago
  Glad to see someone on HN mentioning Strawberry! Hope you're enjoying it!
spapas82 11mo ago
Using Django for almost 15 years, almost exclusively, for both business and personal projects. Have tried a lot of other frameworks, nothing clicks so good with me. My only (small) complain with this release would be that they included the task framework but didn't include a task backend and worker. I'd prefer to wait a bit and include everything in the next version.
- LaurensBER 11mo ago
  Perfect should not be the enemy of good, after all Django is the framework for perfectionists with deadlines ;)
- bredren 11mo ago
  Are they planning to include this? It seems like the kind of demarcation point the framework would avoid crossing into.
  - spapas82 11mo ago
    I think they should. Not sure if they will. However Adam Johnson mentioned django-tasks as the reference implementation that may be included in Django here https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/ https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/.
Arbortheus 11mo ago
I love Django. Thanks Django people, keep making great stuff.
cl42 11mo ago
> Background Tasks. Amazing. If this means no more management of Celery workers, then I am so happy! So nice to have this directly built _into_ Django, especially for very simple task scheduling.
- HiPhish 11mo ago
  You will have to keep Celery for the foreseeable future. The current implementation is just a stub which provides a unified interface for some future backends.
- JodieBenitez 11mo ago
  Background tasks production backend is unfortunately the battery that is not included. Meanwhile, Huey works just fine: https://huey.readthedocs.io/en/latest/django.html https://huey.readthedocs.io/en/latest/django.html
  - no_wizard 11mo ago
    I remember huey! Glad to see leifer is still maintaining it. I liked it way back when it first came out, was a breathe of fresh air compared to celery
- gonational 11mo ago
  Try RQ.
Genego 11mo ago
Django has been one of the biggest reasons why web development has been so enjoyable to me. Whenever I switched to something else, I just felt too spoiled by everything that Django gives you. So I always ended up back with Django, and have no regrets at all specializing deep down that path.
- stanislavb 11mo ago
  Have you tried Ruby on Rails. That's my experience with Rails. Everytime I've tried something else (for web dev), I just felt too spoiled with Ruby & Rails and went back. This includes Django and Phoenix (Elixir). Edit: The only thing that Rails lacks is a decent Admin UI included as part of Rails. I know that there are some external gems that can be used, yet that's something that should be part of the framework in my opinion.
  - rkuykendall-com 11mo ago
    Even before you get to the lacking Admin UI, the first thing Rails asks me to do is implement authentication. Coming from a true batteries-included framework like Django that feels like a complete non-starter.
    - jasondjk 11mo ago
      Rails now provides an authentication generator that creates a super terse but fully customisable auth capability. Here’s an example: https://insidertrades.directory/built-with-rails/google-signin-with-rails-authentication-generator?utm_source=hndec25-djangopost https://insidertrades.directory/built-with-rails/google-sign...
  - sgt 11mo ago
    I use Django a lot and it's great, but even I have to admit that Ruby on Rails is better. It's just that I don't really do a lot of Ruby, so I ended up on the familiar tech stack, and also finding other developers to join a project is much easier with Python.
- scotty79 11mo ago
sergiotapia 11mo ago
Django needs a marketing push. I opened the website and immediately it smells like a 2011 web framework. Like CakePHP. Like Zend. Like Kohana. The site makes the project feel extremely dated, which of course I have no idea how true that is, I've never used Django! Just my 2c from an outsider. I compare it to Phoenix and Rails. (again, talking PURELY marketing here dudes!) https://www.phoenixframework.org/ https://www.phoenixframework.org/ https://rubyonrails.org/ https://rubyonrails.org/
- esperent 11mo ago
  I used Django for a project a couple of years ago. Of course, there's a lot to learn. But generally I found that everything makes sense and I was able to build a moderately complex site with user accounts within a reasonable time. Work took me in different directions, but if a project came up I'd use it again, no problem. Last year I taught myself Next.js for a project. Everyone would say that's a modern framework, with a modern website. I already know React, I'm quite familiar with prisma.js. Learning and using it was (and is, because now I have to maintain the project) painful, confusing, and full of footguns. I wanted to host on Cloudflare but half the stuff doesn't work so I'm forced into Vercel. Takes ages to understand how images work, how server side works, and so on, and those things are still confusing to me. Constantly I ran into tricky problem about getting data to a client side component, or server side, because some UI library wasn't server side or something like that. Even getting the two fonts I'd chosen into a client side component took me several hours! And I still felt like the solution I came up with was hacky and fighting against the framework. I regret learning the "modern" framework. I don't regret learning Django. Don't let fancy marketing fool you into using a bad tool, or drive you away from a good one. Don't judge a web framework by it's website.
- abenga 11mo ago
  I trust them more precisely because they are not wasting resources making slick start-upy marketing fluff that make it difficult to find the actual information I am looking for.
theoldgreybeard 11mo ago
Django is awesome. I just prefer Rails because I prefer Ruby as a language. If you like Python then Django will get you very far.
- linkage 11mo ago
  Ruby is a far better language from a design standpoint and Rails is a better framework in both design and maturity. Sadly, Ruby is a domain-specific language for web backends these days. Most new startups pick Python and TS for their versatility.
nickjj 11mo ago
Congrats to the Django team! If anyone is curious, I've been maintaining a Docker Compose based Django + Celery + Postgres + Redis + esbuild + Tailwind starter app for years and just updated it for Django 6.0 at https://github.com/nickjj/docker-django-example https://github.com/nickjj/docker-django-example. The only thing I haven't done is pre-configure the new CSP settings because I want to let that marinate a bit before putting it in as a default.
- Vaslo 11mo ago
  Very cool and can tell you keep up with it just with your addition of uv!
  - nickjj 11mo ago
    Thanks. Switching to uv ~6-7 months ago was so worth it. It took like 3 seconds to repackage this project thanks to uv, that's building and locking every dependency with Docker too.
- leetrout 11mo ago
  All of Nick's repos are top notch and I high recommend them and reference them from my materials as well. Nick, thank you for sharing so much in the open.
- tclancy 11mo ago
  Thanks. Just went to bookmark it, but pinboard says I already did so in December of 2023.
- droptablemain 11mo ago
  Hah, I used this a few years back on a project. Great work!
yakkomajuri 11mo ago
Django is awesome. Congrats team on the release! Sad to see so little stuff related to async though :(
varun_ch 11mo ago
I worked at an org which has a ‘modern’ NodeJS+React codebase and an ancient legacy Django app on Python 2.7 which is nearing 15 years old. I was worried that the old codebase would be a pain to work on. It was the complete other way around. The Django app was a complete joy to work with and I literally had so much fun tidying it up and working with it that I’ll be sad when they finally retire it in favor of the new new Go/React rewrite.
- chistev 11mo ago
  Why would they retire it? If it ain't broke...
  - SteveNuts 11mo ago
    It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
    - gusgus01 11mo ago
      I just verified. You can install Python 2.7 on an up to date Windows install as well as an up to date Linux install. Python 2.7 hasn't received security updates (or really any updates) in years, but that does not mean it can't still work on an up to date OS.
      - uniqueuid 11mo ago
        The latest 2.7 seems to have a lot of CVEs (did not verify that manually though) https://www.cvedetails.com/version-list/10210/18230/10/Python-Python.html?sha=3b5532b84e25b1f44172dc39fec9f0731496bdf5&order=1&trc=589 https://www.cvedetails.com/version-list/10210/18230/10/Pytho... IIRC some commercial distros maintain patches for 2.7 but then you're paying for being 15 years behind the future.
        gusgus01 11mo ago
        Yeah, it's been 5 years (almost 6) since python 2.7 stopped receiving security updates, but it does still run on modern OS's. Looking at the list, I'm actually kind of surprised there aren't more CVEs for python 2.7, but if you're only running it locally or on an intranet I could see letting it ride.
ducdetronquito 11mo ago
Good job, template partials looks like a nice improvement ! That being said, the current state of type annotations is a pain: django-stubs works on mypy but with a plugin (and mypy is slow as hell), django-types is a fork a django-stubs that works on pyright but is usually out of sync and pylance ships its owned stubs forked from django-types. My biggest wish for next Django release would be that they finally ship type annotations themselves where it is possible. I don't need the crazy inheritance parts or the crazy stringly typed parts to be have proper type annotations, but just some simple stuff like HttpRequest, HttpResponse, View, Model, etc would help a LOT !
- gonational 11mo ago
  I agree, type annotations need work. I just use stubs and then I have some rules to set some of the more common ones to be warnings instead of errors, and then I just deal with the fact that there's gonna be some yellow squiggles.
- franga2000 11mo ago
  I have the same issues in Zed and VS Code, but somehow everything works in PyCharm. Even all the double underscore nonsense in QuerySets that I've never seen work enywhere else. I don't use it very often because I mostly work from my potato of a laptop these days, but when I really just need to Get Shit Done, I sacrifice 10 browser tabs to reclaim some RAM and open PyCharm.
  - f311a 11mo ago
    Pycharm does not have good type checking. It has the best type inference, but its type checking is very basic. It’s not strict, that’s why you don’t see a lot of errors. When complex types don’t much, it won’t complain.
gonational 11mo ago
I see a lot of people in here talking about the "batteries included" aspect of Django, as if that's where it really shines. those batteries are definitely helpful, but the biggest benefit, by far, is the absolute best ORM in existence. If somebody were to reproduce the Django ORM, with full native asynchronous support, it would change Python forever. I know there are people who come from SQLAlchemy and swear by it. As somebody who has used both I can tell you, at least when working with a small team on enterprise software, the ORM blows SQLAlchemy out of the water, in terms of being able to produce quality software, quickly. For anyone new out there thinking about using FastAPI... don't. You'll find 1 million people on the Internet happy to tell you that it's terrific, and 90% of these people have not built real software. The performance gains are lost, by double when you attempt to build real real software with it. I've worked with it in three different apps, and in all three cases it was used because the front end team insisted that all we needed was REST. In all three cases I have seen page load times that are slower than the 90s, 3 to 10 seconds or more before everything is done on the page. It's actually unbelievable to me that that is the direction a lot of Python backend development has gone in, relegating all the important logic, and, in a lot of cases, security, to frontend niceties.
- r1290 11mo ago
  This x1000. I’ve tried every orm in node and nothing compares to Django orm. The way you can scaffold an apps data models is amazing.
  - gonational 11mo ago
    Yeah it's crazy, people use Django and they think the things that are making them productive are all these little contribs and built-ins, but the reality is it's the solid foundation that is the ORM. BTW, I discovered after writing my comment that tortoise ORM is essentially Django ORM, but written on asyncpg, making it way faster. So, if you're stuck in some other non-Django framework and would like to use the Django ORM, that's probably your closest bet.
novoreorx 11mo ago
https://django-ninja.dev/ https://django-ninja.dev/ should be mentioned in this discussion, it's the best thing happen to my 12 years Django career

391 points by wilhelmklopp 11mo ago

Show of hands for backend web services development - Who uses Django, Rails, or similar full-featured frameworks? Who uses micro-frameworks like Flask? Who uses enterprise Java, Jetty, Dot Net, etc.? Who uses an entirely Javascript stack? Who uses a non-traditional language that has become more web-servicey, like Go, Rust, or Swift? Who uses something so wildly untraditional that it's barely mentioned? OkCupid using C++, etc.? Who uses an entirely custom framework (in any language)? Would really love to see a break down of who is using what, how people feel about their tech stack, etc.?

justinator 11mo ago
Perl, CGI.
- echelon 11mo ago
  Love it! Which version of Perl are you using, and what type of service(s) are you maintaining? Is this older software, or do you use it for new projects too? Have you rolled any sort of framework yourself? What are your thoughts on Raku?
  - justinator 11mo ago
    I target 5.10.1 mostly. This is for a project I started in the late 90's. It uses CGI::Application, which is less a framework and more a method lookup table converter of queries (although I built a path info convertor on top of that). It's still maintained, although before Covid, it was my livelihood. About a quarter of a million lines of code, excluding the libraries I pull in. I'm mostly self-taught, they wouldn't even let me get a minor in Comp Sci, since I didn't have the math background (Needed Calculus, I completeled Algebra 2 in hs). Boneheaded Uni. Raku: Second-system effect poster boy. Sensationally dysfunctional community. I think Pugs is what was actually really incredible and Audrey is probably one of the most intelligent people in... the World? Up for contention, but top 10.
    - samtregar3 11mo ago
      [dead]
yoavm 11mo ago
I still have some very old Django projects that I'm maintaining for > 15 years. It's an absolute delight.
- collinmanderson 11mo ago
  Yes. I'm still maintaining a Django site that I helped get live in 2007. I started learning Django in 2006.
hecanjog 11mo ago
This would make an interesting poll. I think that's possible here? Maybe with some karma threshold, I don't seem to be able to make one. We use flask and go at work. I've been micro-framework or roll-my-own-framework most of my career. Go is new for me though, and it's grown on me enough that it's what I prefer for new web-facing projects even for little personal things.
- echelon 11mo ago
  What should the options be? Were the ones I suggested coarse grained enough to capture everyone, or should I/we re-group or add more?
thewebguyd 11mo ago
I"m almost entirely dotnet these days, with a smattering of Go here and there. I work in ops though, so I'm not building consumer-facing products but mostly IT glue code and internal tooling (mostly Go), dashboards, business report generators, gluing SaaS together, etc. (mostly dotnet/C#).
tcdent 11mo ago
I started using Django before the official 1.0 release and used it almost exclusively for years on web projects. Lately I prefer to mix my own tooling and a couple major packages in for backends (FastAPI, SQLAchemy) that are still heavily inspired by patterns I picked up while using Django. I end up with a little more boilerplate, but I also end up with a little more stylistic flexibility.
- BeetleB 11mo ago
  > I started using Django before the official 1.0 release Indeed. I'm still using the 0.97beta. It's perfectly good for production use! </obscure joke>
wg0 11mo ago
- Have written Rails and Django both - Have written SPAs (React/Svelte) - Have written Go based services Each has their on pros and cons.
bossyTeacher 11mo ago
Fable (just for the fun of it) and the new one dot net one file web services that resemble flask
alberth 11mo ago
One proxy might be to look at the upvote counts for each of their respective latest release HN posts. Eg, this post has ~50 (though only posted an hour ago) Rails 8 had ~550 https://news.ycombinator.com/item?id=41766515 https://news.ycombinator.com/item?id=41766515
- echelon 11mo ago
  Rails might not get a lot of new articles about it, and the chatter might have died down, but I think a lot of people still use it.
- canadiantim 11mo ago
  It’s amazing how much rails devs feel the need to denigrate Django, feels like an inferiority complex.
rabbitvictor 11mo ago
At work, it is mainly Kotlin and Go webservices with some Rust for very specific use cases
debugnik 11mo ago
In what sense is Go not a traditional language for web services? They're almost the only thing it's good at, and it's been doing them for 13 years.
- monooso 11mo ago
  I agree that Go is a good choice for web services. I disagree that it's the only thing Go is good at. DevOps tooling and CLI tools immediately spring to mind.
  - debugnik 11mo ago
    Fair, CLI tools is why I said almost, but there's much more competition there. I wouldn't consider devops tools to be its own category though.
aerhardt 11mo ago
As fully-featured as possible, because as much as I like building stuff, I don’t give a shit about coding stuff that has been figured out since the 90’s. Another question is whether semantics and operations get bloated or affect development speed in a framework but I don’t think it’s the case with the Django.
rick1290 11mo ago
Would love to see this. Django just makes life 1000x easier. Can architect an app with data models, api, openapi, etc. within an hour.
zelphirkalt 11mo ago
In a company that uses a traditional web framework like Django to actually build the frontend and backend, not just as only for implementing the APIs, I would even consider doing parts of frontend work again, making everything responsive and so on. That's what I do for a not-yet-startup project.
codr7 11mo ago
I've done several custom frameworks for solo projects in Java & Go, all based on server generated content, inspired by Seaside but more RESTy. Also used Flask and similar libraries for back ends. Did one project in Rails, which was a pretty bad experience in comparison, and killed any motivation to look into Django. Also did plenty of Spring in Java professionally, unfortunately.
kstrauser 11mo ago
Flask is my go-to, but I've had great fun with Rust recently. Django is the best thing in the world for writing Django apps. (No, I'm not trying to be funny there. If what you're doing looks like something Django would solve, it's fantastic.) But most of the things I do aren't Django apps, and ones you get off its happy path, you can be in for a world of hurt. Oh, you use SQLAlchemy everywhere else, and you'd like to use it in your Django app so that you can have one set of models and re-use the service logic you've built? Hah, too bad! Or you need your REST API output to look a very specific way? Have fun with that! Your auth model doesn't look just like Django's? Hope your LLM is good at smoothing that over! The good side is that it's an opinionated framework that does a lot of research on your behalf and makes some great choices. The bad side is that you better agree with its opinions or you're in for a bad time.

nadermx 11mo ago

Django's batteries included setup makes it a no brainer for almost any project big or small. Kudos to the team and contributers

ianberdin 11mo ago

Thanks to Django. I got into the webdev world so easily. Curious, how come Django started to make major versions instead of 1.*? Can be the decreasing in popularity the reason to make Something to change it?

yoavm 11mo ago
It didn't - https://www.djangoproject.com/download/#supported-versions https://www.djangoproject.com/download/#supported-versions
- ianberdin 11mo ago
  Oh, looks more transparent.
- Muromec 11mo ago
  It's amazing, that django docs look and feel exactly the same the did in 0.9x. Damn kids with their JS bullshit have to change the whole site between v1 and v2 and then again when v3 happens. Links rot, API index is hidden and instead of text you get a dump of TS interfaces with zero comments. /rant

sparklingmango 11mo ago

Whenever I use Django, I enjoy it. Simple as.

ChrisArchitect 11mo ago

Blog post yesterday: https://www.djangoproject.com/weblog/2025/dec/03/django-60-released/ https://www.djangoproject.com/weblog/2025/dec/03/django-60-r... (https://news.ycombinator.com/item?id=46136516 https://news.ycombinator.com/item?id=46136516)

wg0 11mo ago

Can someone remind me how we ended up in the SPA era and why exactly? Was it about not seeing the loading spinner? Or there were more reasons to it?

jorl17 11mo ago
- Strict team separation (frontend versus backend) - Moving all state-managament out of the backend and onto the frontend, in a supposedly easier to manage system - Page refreshes are indeed jarring to users and more prone to leading to sudden context losses - Desktop applications did not behave like web apps: they are "SPA"s in their own sense, without jarring refreshes or code that gets "yanked" out of execution. Since the OS has been increasingly abstracted under the browser, and the average computer user has moved more and more towards web apps[1], it stands to reason that the behavior of web apps should become more like that of desktop apps (i.e. "SPA"s)[2] (Not saying I agree with these, merely pointing them out) [1] These things are not entirely independent. It can be argued that the same powers that be (big corps) that pushed SPAs onto users are also pushing the "browser as OS" concept. [2] I know you can get desktop-like behavior from non-SPAs, but it is definitely not as easy to do it or at least to _learn it_ now. My actual opinion: I think it's a little bit of everything, with a big part of it coming from the fact that the web was the easiest way to build something that you could share with people effortlessly. Sharing desktop apps wasn't particularly easy (different targets, java was never truly run everywhere, etc.), but to share a webapp app you just put it online very quickly and have someone else point their browser to a URL -- often all they'll do is click a link! And in general it is definitely easier to build an SPA (from the frontender's perspective) than something else. This creates a chain: If I can create and share easily -> I am motivated to do things easily -> I learn the specific technology that is easiest -> the market is flooded with people who know this technology better than everything else -> the market must now hire from this pool to get the cheapest workers (or those who cost less to acquire due to quicker hiring processes) -> new devs know that they need to learn this technology to get hired -> the cycle continues So, TL;DR: Much lower barrier to entry + quick feedback loops P.S (and on topic): I am an extremely satisfied django developer, and very very very rarely touch frontend. Django is A-M-A-Z-I-N-G.
- 11mo ago

sroerick 11mo ago

Django was my first big freelance project, and still feels tremendously cozy to use. I've done some goofy things with it and it's always served me really well. Thank you Django

alex1138 11mo ago

[flagged]

willahmad 11mo ago

Django is awesome, but I wish there was an easy way to use modern web frameworks with it. A lot of times it's either through Nextjs/Nuxtjs + Django as an API or complex bundling process which requires a file where you register bundle versions/manifests then another build process which embeds them into template both are so complex

stevex 11mo ago
Django + AlpineJS + HTMX is pretty nice.
- FartinMowler 11mo ago
  Especially with template partials now in the core of Django 6.
- HiPhish 11mo ago
  That's just for the HTML content though. What if you want to add some non-trivial Javascript or generated CSS? Or maybe you want to integrate a frontend tool like Storybook[0] even if your HTML is rendered server-side? Maybe add some tests for your frontend code? There is much more between raw hand-rolled HTML/CSS/JS and a full-blown SPA. At my day job we use Django with HTMX and Alpine, but we also generate the custom CSS from Pico[1] and use JinjaX[2] to define server-side components which we then render in Storybook. We use Vue as our bundler to compile the JS and CSS as well as to run Storybook. The project has to live in both the Python ecosystem and the Node.js ecosystem. Even with just HTMX and Alpine you might want to compile a custom version of those with certain plugins, or you might want to load them as libraries in your own scripts. [0] https://storybook.js.org/ https://storybook.js.org/ [1] https://picocss.com/ https://picocss.com/ [2] https://jinjax.scaletti.dev/ https://jinjax.scaletti.dev/
  - michaelyin 11mo ago
    [dead]
mushufasa 11mo ago

stevex 11mo ago

One thing Django has going for it is that the "batteries included" nature of it is perfect for AI code generation. You can get a working site with the usual featuers (admin panel, logins, forgot reset/password flow, etc) with minimal code thanks to the richness of the ecosystem, and because of the minimal code it's relatively easy for the AI to keep iterating on it since it's small enough to be understandable in context.

throwawaymaths 11mo ago
why would you need batteries included? the ai can code most integrations (from scratch, if you want, so if you need something slightly off the beaten path it's easy
- jorl17 11mo ago
  I think the logic can be applied to humans as well as AI: Sure, the AI _can_ code integrations, but it now has to maintain them, and might be tempted to modify them when it doesn't need to (leaky abstractions), adding cognitive load (in LLM parlance: "context pollution") and leading to worse results. Batteries-included = AI and humans write less code, get more "headspace"/"free context" to focus on what "really matters". As a very very heavy LLM user, I also notice that projects tend to be much easier for LLMs (and humans alike) to work on when they use opinionated well-established frameworks. Nonetheless, I'm positive in a couple of years we'll have found a way for LLMs to be equally good, if not better, with other frameworks. I think we'll find mechanisms to have LLMs learn libraries and projects on the fly much better. I can imagine crazy scenarios where LLMs train smaller LLMs on project parts or libraries so they don't get context pollution but also don't need a full-retraining (or incredibly pricey inference). I can also think of a system in line with Anthropic's view of skills, where LLMs very intelligently switch their knowledge on or off. The technology isn't there yet, but we're moving FAST! Love this era!!
  - codr7 11mo ago
    Maybe if they could learn how to switch their intelligence on, that would help more?

personjerry 11mo ago

Do you guys find Django includes enough batteries? Why or why not? I find myself using Cookiecutter Django [^1] more often than not, better auth, a bunch of boilerplate configs, S3 and email setups if you want, and other stuff rather than have to jiggle with "Django infra" myself [^1]: https://github.com/cookiecutter/cookiecutter-django https://github.com/cookiecutter/cookiecutter-django

gnulinux996 11mo ago

What is the Java equivalent of Django? I really love django and everything around it, but I would also like to write a webapp in Java. Getting django + rest_framework up and running and actually be productive takes me max 10 minutes, trying to do the same with spring boot I am a week in and I had to open the jakarta specs to understand the magic.

frikk 11mo ago
How about this? https://github.com/dropwizard/dropwizard https://github.com/dropwizard/dropwizard
atomicnumber3 11mo ago
Java honestly just does not have this. By the time java collectively decided that being able to spend your time writing your actual product instead of fucking with config shit forever, the age of the monolithic SSR templated backend app were gone. So now most modern things like helidon focus on being microservicey like go, or they have very soft template rendering offerings and don't really do batteries included. I feel your pain, I myself am working on a react frontend + spring boot backend and fiddling with it to integrate with spring session, security, etc properly was a HUGE pain because neither world knows anything at all about each other. If I did it from scratch I'd just "rails new myapp" and be done already.
- haolez 11mo ago
  Isn't there Thymeleaf that alleviates that?
  - atomicnumber3 11mo ago
    Forgive me, but thyme leaf is soft compared to ERB and jinja.
frio 11mo ago
I'm not sure why people aren't saying Spring Boot, but Spring Boot. Yeah it has heaps of other batteries included, and it doesn't have a built-in admin, but it gives you pretty decent stuff out of the box

blorenz 11mo ago

Django powers my SaaS. I use it mainly as a data backend with its ORM, admin, and incorporate Strawberry graphql into it for the data exchange to my frontends. I wish it was better with async, though.

patrick91 11mo ago
Glad to see someone on HN mentioning Strawberry! Hope you're enjoying it!

spapas82 11mo ago

Using Django for almost 15 years, almost exclusively, for both business and personal projects. Have tried a lot of other frameworks, nothing clicks so good with me. My only (small) complain with this release would be that they included the task framework but didn't include a task backend and worker. I'd prefer to wait a bit and include everything in the next version.

LaurensBER 11mo ago
Perfect should not be the enemy of good, after all Django is the framework for perfectionists with deadlines ;)
bredren 11mo ago
Are they planning to include this? It seems like the kind of demarcation point the framework would avoid crossing into.
- spapas82 11mo ago
  I think they should. Not sure if they will. However Adam Johnson mentioned django-tasks as the reference implementation that may be included in Django here https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/ https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/.

Arbortheus 11mo ago

I love Django. Thanks Django people, keep making great stuff.

cl42 11mo ago

> Background Tasks. Amazing. If this means no more management of Celery workers, then I am so happy! So nice to have this directly built _into_ Django, especially for very simple task scheduling.

HiPhish 11mo ago
You will have to keep Celery for the foreseeable future. The current implementation is just a stub which provides a unified interface for some future backends.
JodieBenitez 11mo ago
Background tasks production backend is unfortunately the battery that is not included. Meanwhile, Huey works just fine: https://huey.readthedocs.io/en/latest/django.html https://huey.readthedocs.io/en/latest/django.html
- no_wizard 11mo ago
  I remember huey! Glad to see leifer is still maintaining it. I liked it way back when it first came out, was a breathe of fresh air compared to celery
gonational 11mo ago
Try RQ.

Genego 11mo ago

Django has been one of the biggest reasons why web development has been so enjoyable to me. Whenever I switched to something else, I just felt too spoiled by everything that Django gives you. So I always ended up back with Django, and have no regrets at all specializing deep down that path.

stanislavb 11mo ago
Have you tried Ruby on Rails. That's my experience with Rails. Everytime I've tried something else (for web dev), I just felt too spoiled with Ruby & Rails and went back. This includes Django and Phoenix (Elixir). Edit: The only thing that Rails lacks is a decent Admin UI included as part of Rails. I know that there are some external gems that can be used, yet that's something that should be part of the framework in my opinion.
- rkuykendall-com 11mo ago
  Even before you get to the lacking Admin UI, the first thing Rails asks me to do is implement authentication. Coming from a true batteries-included framework like Django that feels like a complete non-starter.
  - jasondjk 11mo ago
    Rails now provides an authentication generator that creates a super terse but fully customisable auth capability. Here’s an example: https://insidertrades.directory/built-with-rails/google-signin-with-rails-authentication-generator?utm_source=hndec25-djangopost https://insidertrades.directory/built-with-rails/google-sign...
- sgt 11mo ago
  I use Django a lot and it's great, but even I have to admit that Ruby on Rails is better. It's just that I don't really do a lot of Ruby, so I ended up on the familiar tech stack, and also finding other developers to join a project is much easier with Python.
scotty79 11mo ago

sergiotapia 11mo ago

Django needs a marketing push. I opened the website and immediately it smells like a 2011 web framework. Like CakePHP. Like Zend. Like Kohana. The site makes the project feel extremely dated, which of course I have no idea how true that is, I've never used Django! Just my 2c from an outsider. I compare it to Phoenix and Rails. (again, talking PURELY marketing here dudes!) https://www.phoenixframework.org/ https://www.phoenixframework.org/ https://rubyonrails.org/ https://rubyonrails.org/

esperent 11mo ago
I used Django for a project a couple of years ago. Of course, there's a lot to learn. But generally I found that everything makes sense and I was able to build a moderately complex site with user accounts within a reasonable time. Work took me in different directions, but if a project came up I'd use it again, no problem. Last year I taught myself Next.js for a project. Everyone would say that's a modern framework, with a modern website. I already know React, I'm quite familiar with prisma.js. Learning and using it was (and is, because now I have to maintain the project) painful, confusing, and full of footguns. I wanted to host on Cloudflare but half the stuff doesn't work so I'm forced into Vercel. Takes ages to understand how images work, how server side works, and so on, and those things are still confusing to me. Constantly I ran into tricky problem about getting data to a client side component, or server side, because some UI library wasn't server side or something like that. Even getting the two fonts I'd chosen into a client side component took me several hours! And I still felt like the solution I came up with was hacky and fighting against the framework. I regret learning the "modern" framework. I don't regret learning Django. Don't let fancy marketing fool you into using a bad tool, or drive you away from a good one. Don't judge a web framework by it's website.
abenga 11mo ago
I trust them more precisely because they are not wasting resources making slick start-upy marketing fluff that make it difficult to find the actual information I am looking for.

theoldgreybeard 11mo ago

Django is awesome. I just prefer Rails because I prefer Ruby as a language. If you like Python then Django will get you very far.

linkage 11mo ago
Ruby is a far better language from a design standpoint and Rails is a better framework in both design and maturity. Sadly, Ruby is a domain-specific language for web backends these days. Most new startups pick Python and TS for their versatility.

nickjj 11mo ago

Congrats to the Django team! If anyone is curious, I've been maintaining a Docker Compose based Django + Celery + Postgres + Redis + esbuild + Tailwind starter app for years and just updated it for Django 6.0 at https://github.com/nickjj/docker-django-example https://github.com/nickjj/docker-django-example. The only thing I haven't done is pre-configure the new CSP settings because I want to let that marinate a bit before putting it in as a default.

Vaslo 11mo ago
Very cool and can tell you keep up with it just with your addition of uv!
- nickjj 11mo ago
  Thanks. Switching to uv ~6-7 months ago was so worth it. It took like 3 seconds to repackage this project thanks to uv, that's building and locking every dependency with Docker too.
leetrout 11mo ago
All of Nick's repos are top notch and I high recommend them and reference them from my materials as well. Nick, thank you for sharing so much in the open.
tclancy 11mo ago
Thanks. Just went to bookmark it, but pinboard says I already did so in December of 2023.
droptablemain 11mo ago
Hah, I used this a few years back on a project. Great work!

yakkomajuri 11mo ago

Django is awesome. Congrats team on the release! Sad to see so little stuff related to async though :(

varun_ch 11mo ago

I worked at an org which has a ‘modern’ NodeJS+React codebase and an ancient legacy Django app on Python 2.7 which is nearing 15 years old. I was worried that the old codebase would be a pain to work on. It was the complete other way around. The Django app was a complete joy to work with and I literally had so much fun tidying it up and working with it that I’ll be sad when they finally retire it in favor of the new new Go/React rewrite.

chistev 11mo ago
Why would they retire it? If it ain't broke...
- SteveNuts 11mo ago
  It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
  - gusgus01 11mo ago
    I just verified. You can install Python 2.7 on an up to date Windows install as well as an up to date Linux install. Python 2.7 hasn't received security updates (or really any updates) in years, but that does not mean it can't still work on an up to date OS.
    - uniqueuid 11mo ago
      The latest 2.7 seems to have a lot of CVEs (did not verify that manually though) https://www.cvedetails.com/version-list/10210/18230/10/Python-Python.html?sha=3b5532b84e25b1f44172dc39fec9f0731496bdf5&order=1&trc=589 https://www.cvedetails.com/version-list/10210/18230/10/Pytho... IIRC some commercial distros maintain patches for 2.7 but then you're paying for being 15 years behind the future.
      - gusgus01 11mo ago
        Yeah, it's been 5 years (almost 6) since python 2.7 stopped receiving security updates, but it does still run on modern OS's. Looking at the list, I'm actually kind of surprised there aren't more CVEs for python 2.7, but if you're only running it locally or on an intranet I could see letting it ride.

ducdetronquito 11mo ago

Good job, template partials looks like a nice improvement ! That being said, the current state of type annotations is a pain: django-stubs works on mypy but with a plugin (and mypy is slow as hell), django-types is a fork a django-stubs that works on pyright but is usually out of sync and pylance ships its owned stubs forked from django-types. My biggest wish for next Django release would be that they finally ship type annotations themselves where it is possible. I don't need the crazy inheritance parts or the crazy stringly typed parts to be have proper type annotations, but just some simple stuff like HttpRequest, HttpResponse, View, Model, etc would help a LOT !

gonational 11mo ago
I agree, type annotations need work. I just use stubs and then I have some rules to set some of the more common ones to be warnings instead of errors, and then I just deal with the fact that there's gonna be some yellow squiggles.
franga2000 11mo ago
I have the same issues in Zed and VS Code, but somehow everything works in PyCharm. Even all the double underscore nonsense in QuerySets that I've never seen work enywhere else. I don't use it very often because I mostly work from my potato of a laptop these days, but when I really just need to Get Shit Done, I sacrifice 10 browser tabs to reclaim some RAM and open PyCharm.
- f311a 11mo ago
  Pycharm does not have good type checking. It has the best type inference, but its type checking is very basic. It’s not strict, that’s why you don’t see a lot of errors. When complex types don’t much, it won’t complain.

gonational 11mo ago

I see a lot of people in here talking about the "batteries included" aspect of Django, as if that's where it really shines. those batteries are definitely helpful, but the biggest benefit, by far, is the absolute best ORM in existence. If somebody were to reproduce the Django ORM, with full native asynchronous support, it would change Python forever. I know there are people who come from SQLAlchemy and swear by it. As somebody who has used both I can tell you, at least when working with a small team on enterprise software, the ORM blows SQLAlchemy out of the water, in terms of being able to produce quality software, quickly. For anyone new out there thinking about using FastAPI... don't. You'll find 1 million people on the Internet happy to tell you that it's terrific, and 90% of these people have not built real software. The performance gains are lost, by double when you attempt to build real real software with it. I've worked with it in three different apps, and in all three cases it was used because the front end team insisted that all we needed was REST. In all three cases I have seen page load times that are slower than the 90s, 3 to 10 seconds or more before everything is done on the page. It's actually unbelievable to me that that is the direction a lot of Python backend development has gone in, relegating all the important logic, and, in a lot of cases, security, to frontend niceties.

r1290 11mo ago
This x1000. I’ve tried every orm in node and nothing compares to Django orm. The way you can scaffold an apps data models is amazing.
- gonational 11mo ago
  Yeah it's crazy, people use Django and they think the things that are making them productive are all these little contribs and built-ins, but the reality is it's the solid foundation that is the ORM. BTW, I discovered after writing my comment that tortoise ORM is essentially Django ORM, but written on asyncpg, making it way faster. So, if you're stuck in some other non-Django framework and would like to use the Django ORM, that's probably your closest bet.

novoreorx 11mo ago

https://django-ninja.dev/ https://django-ninja.dev/ should be mentioned in this discussion, it's the best thing happen to my 12 years Django career