Not a hindrance, but something like not having a typed database, no auto completion over time, can be a real drawback (I know about django-types).
Finally, in my opinion, the best reason to not use Django is not the project itself (because it will do the job in 99% case), it's because all you learn is tied to Django.
Having learn Pydantic recently was a breed of fresh air, and I would reuse it in lots of projects, not only web projects.
+1 on this. Django scales pretty well when adopting a clean architecture like Django Model Behaviours with mixins.
> Otherwise, I've found its ORM quite powerful.
Same. In ten years, the only issue I had is with a very complex query that the ORM was not able to write properly. But a workaround existed.
I'm currently using FastAPI in a project. It's very enjoyable (especially with a strictly typed codebase) but I have to write lots of batteries by myself, which is not very productive (unless you keep this boilerplate code for future projects).
What's a little frustrating with current webdev state if that there is no silver bullet. I can easily think of use case where a Django+htmx stack is much more relevant than a React/Vue one, but the opposite is true too.
People keep genuinely saying it's a good thing to have many tools to apply to the right usage. Personnaly, constantly switching from htmx to vue.js just fucks my brain.
I miss the time where I used Django or Rails and didn't need to ask myself all these questions.
Finally, in my opinion, the best reason to not use Django is not the project itself (because it will do the job in 99% case), it's because all you learn is tied to Django.
Having learn Pydantic recently was a breed of fresh air, and I would reuse it in lots of projects, not only web projects.