Regarding my edit, you need to differentiate between different types of jobs. Sending an email is okay to do in process. Other (mostly async) Python web frameworks have implemented this, so the Django team probably felt compelled to offer the same. Processing a user-uploaded file is much more expensive and shouldn't be done in the web process. If enough users upload files you're starving your workers for CPU.

Edit: Background tasks for light work are also included in this release.

Citation needed. I'd imagine they just add a tiny markup to their prices to pay the eventual fine instead of investing huge amounts of money into fixing their broken processes. Comparing the list of EU-issued fines against the respective companies' profits shows that they can simply afford to make those mistakes instead of preventing them.

Adding to that, Germany still has no suitable location for a final depot for storing nuclear waste, and the unquantifiable cost to maintain such a depot for tens of thousand of years is often swept under the rug by nuclear supporters.

About the Tesla factory thing, those protests are mostly done by a handful of environmental activists and - most importantly - NIMBYs from the surrounding area.

4. Having the scraped data in Python-land makes it sometimes way easier to dump it into an analysis landscape, which is probably Python, too.

The basic dependencies for the Django admin are:

- authentication

- user permissions

- forms

- the ORM, to generate forms from model definitions and forward the admin's CRUD operations to the database

No other framework comes with all of these dependencies builtin. Yes, there are individual plugins to retrofit them, but then you would start building your extremely complex admin plugin on top of a lot of unaligned dependencies. Just one of them needs to go into a direction that doesn't align with your needs and your project is done. That's not a good base to start from. Django doesn't have this problem because the entire framework is built under one roof.