I agree with what git-pull has commented. In addition to that, addressing your question: * There is value in reusing the tool that you have already used, whet

I agree with what git-pull has commented. In addition to that, addressing your question: * There is value in reusing the tool that you have already used, whether django or flask, because you have accumulated knowledge for doing the common stuff that you can carry from one project to the other trivially, and spend the bulk of your time and what really matters for that project. * IMO, Flask is most suitable for educating oneself on how a web app is structured and what it's crucial features are. With Django, I can only focus on the aspects of the project that matter, and all other bases like security, scalability etc are covered by the django codebase, atleast as long as one follows the best practices. Also, only override existing django parts, if you need to, not because you can. The obligatory anecdote: For one of my projects, I decided Jinja2 was much better than django Templates and switched to Jinja2. And true, the Jinja2's syntax was more versatile than Django Template's. Unfortunately, it took me sometime to realize that by doing the switch, I also lost the ability to use hundreds of plugins for django-template because either they do not interact with Jinja2, or they do so poorly. For a later project, I stuck to django-templates and with a little diligence, I could make it do all that Jinja2 could do too (atleast those features that I found desirable in Jinja2). Never, never, never add unnecessary complication to a project that needs to be shipped.