141–150 of 192 posts
Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
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.
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.
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…
Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
"Fun" isn't the same thing as "functional." I remember having great fun in QuickBASIC. And my son enjoys Scratch. Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way. * I…
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.
Are they planning to include this? It seems like the kind of demarcation point the framework would avoid crossing into.
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/.
Earlier quoted context omitted.
It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
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.
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.
Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
It’s very likely that project is a security nightmare. Just an OS old enough to support 2.7 would be problematic.
Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
"Fun" isn't the same thing as "functional." I remember having great fun in QuickBASIC. And my son enjoys Scratch. Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way. * I…
Plenty of Django businesses making tens of millions. Some in the billions.
I know a solopreneur making around $2m a year and all he uses is Django
Earlier quoted context omitted.
Why would they retire it? If it ain't broke...
"Fun" isn't the same thing as "functional." I remember having great fun in QuickBASIC. And my son enjoys Scratch. Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way. * I…
Earlier quoted context omitted.
Rails tries to more tightly integrate with the front-end which causes a lot of turn over the years. Django projects from 10 years ago are still upgradable in a day or two. Rails does include some nice stuff though, but I much prefer Django's code first database models than Rail's ActiveRecord.
Those Django models are a pain to work with if you have to access the database with any other tool that is not the original Django app. The only sane way to design a database managed by Django models and migrations is not using any inheritance between models or you'll end up with a number of tables, each one adding a few fields. Django ORM will join them for you but you are on your own if you ever have to write queri…
Django does nothing special compared to the way I would design my db tables the completely manual way.