It really comes down to the requirements for your app as defined by the vendor and/or the internal team.
If MS did a better job at supporting headless Windows distros to compete with Debian (and similar linux) distros, it would be more popular.
For 9/ 10 tasks, it's way easier to spin up Debian , install a web / db / app server and have a running solution.
With windows you're still running through dozens of MSI packages, setup screens. It's too inconsistent.
There are workarounds to this, but they are not as mature & familiar as the corresponding linux setup.
It's the UX not the platform.
Batteries included would mean inclusion of the most basic requirement of almost every web application - some sort of user signup/signin/forgot password auth and cookie/token flow. Django does not include anything for this and leaves it to the user to work out - and this tends to be one of the most complex parts of a new system.
But it does: https://docs.djangoproject.com/en/5.0/topics/auth/default/#m...
Does it mention that the AP's will spam network requests with or without a controller on that page?