Re:Django vs. Flask for a long-term project
by mercurial on Thursday January 23, 2014 @02:22AM
(#7107286)
It turns out that you have a Flask-admin plugin:
http://flask-admin.readthedocs.org/en/latest/index.html
I haven't used it, but looking at the quickstart, you gain a lot of flexibility in exchange for a bit of boilerplate. As I haven't done any Django in a long time, I cannot comment on how complete it is, but it shows that you can absolutely achieve this kind of functionality in a framework with a tiny core.
The admin depends on uniform URL conventions driven by the framework and the URL reversion mechanism to get object URLs.
The CRUD DB functionality depends on the models being compatiable with the Django ORM interface, as well as the forms and the interations between the ORM and forms which allows for things like ModelForms.
The admin has its own set of important template tags to render information depending on the context, and that allows for consisten overriding and enhancing of functionality.
The imporant thing is that, even though all those components are decoupled, they were made in mind to interact flawlessly, and share idioms and interfaces that allow them to work together in ways that that more decoupled frameworks do not.
Finally, while there is nothing special about each component per se, most people seriously exaggerate the shortcomings of each, and there is no component in Django that is plainly bad, something that I have personally seen in pretty much every other framework I have worked with. Consistency is important.