I can't speak for the other frameworks, but with Django this would have not been a problem at all. In Django, most "batteries included" features really just are 1st party plugins, i.e. you can choose to not use the builtin authentication stack and bring your own. All of this is officially supported and well documented, e.g. https://docs.djangoproject.com/en/5.1/topics/auth/customizin...
> It is simply cost and money in the face of much cheaper, less risky and heavily abundant renewable energy.
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.
Well, 1978 was a long time ago and environmental concerns weren't a big thing back then. RWE had all rights to do what they did, even the Green party acknowledged that when the Hambach Forest situation escalated.
About the Tesla factory thing, those protests are mostly done by a handful of environmental activists and - most importantly - NIMBYs from the surrounding area.
That's what I was referring to, wondering if anyone uses it and why. It even says "Why This is a Bad Idea" at the bottom.
Maybe for databases queried directly by users who also need to mix in API responses, and you're wrapping this all up in triggers or some other stored procedure cause you really want to use Postgres without some controller written in Python or JS.
The core reason is (imo) that it's simply not possible to provide a Django admin equivalent in other frameworks because they lack the functionality to do so.
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.
Laravel has the foundation for these baked in. And they provided a paid admin packages if you don’t want to implement the rest.
My opinion is that once you add a dependency to your project, you own it just like your own code. This means understanding it enough to know how it’s built, but for the time being, someone else is maintaining it. And that a donation every once in a while should be made if it’s a core part of your product.
That's because psycopg adheres to the DBAPI standard (think of JDBC of the Python world). asyncpg deliberately ignores this standard for huge performance boosts.
