171–180 of 237 posts
Congrats on the release to the Django community! If anyone is curious, I updated my Django / Docker starter app to use Django 5.0 at: https://github.com/nickjj/docker-django-example It pulls together gunicorn, Celery, Redis, Postgres, esbuild and Tailwind with Docker Compose. It's set up to run in both development and production.
Congrats on the release to the Django community! If anyone is curious, I updated my Django / Docker starter app to use Django 5.0 at: https://github.com/nickjj/docker-django-example It pulls together gunicorn, Celery, Redis, Postgres, esbuild and Tailwind with Docker Compose. It's set up to run in both development and production.
3 years ago I moved to fast growing startup that was founded with fast api slap-dashed together. I jammed Django down their throats and I can safely say it was the best decision we made as an Org. The teams using Django are far far more productive than the others. When a product I think is going to need users and roles and permissions, I grab Django off the shelf and never look back. Thank you mister reinhardt
There are so much structural mistakes in our codebase, they use async python but messed it up in all the important places yet believe that Django is slow or innadequate.
They belive that Django is too "old school" and that if you want good results you need vue.js an api and all that.
Truth is, no one has the time and experience to make something good with that.
Developpement is very slow and code is buggy management is unsatisfied with the results yet they refuse to try it out.
It seem their ideas are made up and won't change.
I work in the Rails world, and perhaps my perception is colored by the big changes they tend to make, but this seems like more of a minor than a major version release? Or is this relatively big for Django?
Django releases are now based on a schedule, so the 5.0 label wouldn't have been chosen because of significant changes.
But, I have observed that releases often look like this:
- X.0 Newer shinier features
- X.1 More refinement and minor features
- X.2 [LTS] More refinement and minor features
Which means if you stick to the point 2 releases you get longer support and subjectively more stability since the shiny new features have been polished over a couple of point releases.
But in reality these days, I think it's just whatever features are ready to ship for the scheduled release date.
Earlier quoted context omitted.
We can have 1+N queries in any language even without an ORM. Maybe an ORM facilitates mistakes because it hides joins but lack of experience is lack of experience. Some naive bad pseudocode: for book in select * from books: author = select * from authors where id == book.id print book.title author.name In the real world that nested select could be hidden many levels down in method or function calls or even in code ru…
I'm not criticising ORMs, just how active record works.
Earlier quoted context omitted.
> 6 years later, the Django side needed minimal changes and is up and running (I jumped all the way from 1.11 to 5.0 beta). I've been using Django since before 1.0, and the upgrade story has been nothing short of fantastic for something that's been around this long. But still, YMMV! Depending on how ancient a project you run into, it definitely can be a major pain, even with the original authors' best intentions. For…
> The builtin admin system is also a pretty decent CMS on its own (...) It's wise to get off the builtin admin system as your project grows. And go to another superbly robust and easy to use actual CMS: wagtail.
Earlier quoted context omitted.
I still use JQuery because of all the syntactic sugar and shortcuts.
Me too, I prefer the API. At the end of the day I’m delivering reliable and productive solutions for my clients, and they don’t care what the tech is. However the Django API, GraphQL with React front end stack I’ve inherited is an frustratingly flakey to use and a nightmare to develop :-/ It’s so bad I’m regretting all my life choices that led me to this point LOL
Earlier quoted context omitted.
> 6 years later, the Django side needed minimal changes and is up and running (I jumped all the way from 1.11 to 5.0 beta). I've been using Django since before 1.0, and the upgrade story has been nothing short of fantastic for something that's been around this long. But still, YMMV! Depending on how ancient a project you run into, it definitely can be a major pain, even with the original authors' best intentions. For…
> The builtin admin system is also a pretty decent CMS on its own (...) It's wise to get off the builtin admin system as your project grows. And go to another superbly robust and easy to use actual CMS: wagtail.
Also it's been a few years since I've last used it, but the overwhelming dominance of deeply nested JSON fields makes ordinary DB migrations unnecessarily interesting.
My app is a Django backend and a Vue frontend. There are large swathes of Django that I ignore, but to me the core of Django — its ORM, routing and middleware system, and admin interface — are worth their weight in gold. The migration from DRF to Django-Ninja (which is, roughly, FastAPI + Django) has also been a great improvement in terms of productivity and performance. Not a lot of whizbang features in 5.0, but Gen…
GeneratedField looks interesting, but I'm not _really_ sure what gains I get over just calling annotate() on my queryset with some computed fields. At least on the backends where the computed GeneratedField isn't stored.