71–80 of 191 posts
Love django. Whats the consensus on best way to use django in 2025? I've been going the headless route. Django for the backend and using vite or nextjs on the frontend with openapi specs auto-generated.
As someone today who is an unrelenting critic of python. I have to say thank you to Simon and the Django community as a whole. Its a wonderful "batteries included" framework that has launched many successful projects, companies, and careers. Mine included. And I'd be lying if I didnt say I still use pgadmin as my benchmark for evaluating admin panels in other ecosystems. What you all created with Django is amazing. W…
How can you be an unrelenting critic of Python but love Django?
Specifically for python vs django, most of the things I dont like are actually attributable to decisions by the python team, not necessarily Django.
But many of the things I do like are attributable to the Django team.
Earlier quoted context omitted.
I don't think you can honestly and objectively criticise something you don't truly know. There's still no framework in e.g. Go that comes anywhere close to matching Django. It's pragmatic, doesn't do too much meta-magic (I still don't "get" Rails), lets you strip away any layers you don't need, etc.
I think Phoenix is very close to Django at fitting that bill.
Love django. Whats the consensus on best way to use django in 2025? I've been going the headless route. Django for the backend and using vite or nextjs on the frontend with openapi specs auto-generated.
Love django. Whats the consensus on best way to use django in 2025? I've been going the headless route. Django for the backend and using vite or nextjs on the frontend with openapi specs auto-generated.
It wasn't long before newforms became a thing, and the 1.0 release, lots of cool database features, migrations (I remember debating South vs. Nashvegas at work), class-based views (amazing!), Postgres-specific features (built-in JSONField, finally!), Py3k support, ASGI... It's been a long, cool, productive road.
I was at the first DjangoCon in 2008 (leaving my wife at home with our two month old!), and giving a conference talk for the first time a decade later at DjangoCon 2018.
I owe my career to Django. It has been my framework of choice for projects large and small, and I've always felt solid in that decision -- thanks in no small part to the community.
HBD Django! <3
In a very real sense, I have Django to thank for my entire career. As an undergraduate, my first academic job in a research lab had me building websites to promote the research in a lab. Django was brand new, and I was uninterested in petty concerns like stability and security, so I did everything in Django. Years later (2009), I got to do interesting work in a cutting edge machine learning lab due to the expertise I…
didnt they hear about sqlite, great for this setup
Earlier quoted context omitted.
Does/did Django have a reputation for instability or insecurity? Also, how on Earth did the ML PhDs decide physically segregated databases for each user were a requirement?
It's not that Django has/had any reputation for those things -- it's that Django had no reputation at all since it was a nascent project with no track record. That means it had no proof points for being stable or secure. At the time I adopted it (~Nov 2005), the public release of the Django project was only a few months old, and indeed breaking changes followed soon after (the so-called "magic removal branch"). As I…
Django is somehow the one thing in Python I never enjoyed working on. I recommend it thoroughly to people running teams since it keeps devs disciplined, but I've always been a Flask programmer at heart. To each their own. I'm glad Django exists, it's eaten plenty a share of the pie that would have otherwise gone to Rails maybe.
The drift from a simple Flask to monstrosity Flasknjo was so natural that I suspect it happens to a lot of people.
In a very real sense, I have Django to thank for my entire career. As an undergraduate, my first academic job in a research lab had me building websites to promote the research in a lab. Django was brand new, and I was uninterested in petty concerns like stability and security, so I did everything in Django. Years later (2009), I got to do interesting work in a cutting edge machine learning lab due to the expertise I…