This is a very valid question. The most likely answer is somewhat cruel though.

Looks like an interesting alternative to the bigger Django and FastAPI which get all the attention.

There's a sustainability issue for the REST support with Django. Hopefully this will resolve.

Nice comparison of both approaches. Some of the criteria used I would have left out but otherwise it seems fair.

Django doesn't always generate the migration you'd expect. Read them before going to production. Also it's fine to adjust them.

Little and to the point reference on safer SQLite use. I should check if some of this would apply or is used by Akonadi as well.

Another example of enforcing conventions using automated checks. This time using Python and Django tricks.

Overview of the differences in behavior between the two most popular ORMs in the Python ecosystem. This shows interesting different design options for such things.

This is more manual work of course but too often forgotten. This way you get easier database migrations in complex environments though.

Nice exploration of Django + HTMX + web components for a CRUD use case. Interesting insights and highlights some of the limitations with HTMX.

Another impressive feat from the people behind the Cosmopolitan project. A self contained and portable binary which run your Django application on almost any platform? Apparently doable. The versions used for the dependencies are a bit old but that's clearly something which will be solved soon.

Interesting data point about a service moving completely to the htmx and web components approaches. Not all applications are going to see such drastic improvements, that being said the change in team structure alone feels like a very good thing to me (and is more likely to be the constant in such moves).

A couple of good advises in there for a Django project inception.

Interesting way to combine Django and a couple of JS based tiny frameworks to make simpler frontends.