[motiejus]

OK, a Django update from me.

I heavily used Django since version 0.96 (2007) until 1.5 (2014) (with Python 3)! Then came a long break with lower-level infrastructure work: linux kernel, perf tuning, some C, some Go and zig.

Last week I picked up Django again. After 10 years (!!!) of not even looking at it. It felt like meeting a good old friend: they are the same, but older and more mature. Conversations are the same. But better.

Things change in the tech world, often for the worse. Django changes, as it matures, for the better. The website layout, tutorial, colors, excellent release notes, `./manage.py runserver` are all the same as I remember them.

Except today it's easier, since I am much wiser in deploying and maintaining things than I was a decade ago. :)

[tcdent]

Similar experience. Started on 0.96, used daily until about 2.x and then took a break. Came back last year and was delighted to find most of the API remained stable. Before reading the release notes for Django 5 I was expecting at least a few breaking changes for my 4.2 apps, but there's almost none.

Part of the reason I took a break from tech in the first place was the relentless upgrade cycle. Thrilled that we've solved at least a few of the problems in sustainable ways.

[mrweasel]

Same experience from me. I stopped working with Django around 2016 and then picked up a project last year where we picked Django as the framework and it was like I never left. They added new features, improved documentation and all that, but it was so amazingly easy to come to.

It probably does help that we stick to Django 3.X as that's what's currently in Debian.

I do like the smaller frameworks like Flask or Bottle, but if I need a database or anything remotely more complex than answering a few API calls, then I don't see a reason to not pick Django.