I've done trivial and non-trivial projects in both, and the general summary presented here feels correct. If you've got something with content, that matches mos

I've done trivial and non-trivial projects in both, and the general summary presented here feels correct. If you've got something with content, that matches most common situations (users, content related to users, content related to other content), Django will get you there quickly and efficiently. But I still use Flask a lot more, because most of what I create are limited use web services that do interesting things behind the scenes. Caching proxies to improve performance of legacy services, script runners, report generation tools. Most of the time, Flask feels like the de facto web server, like Requests is the de facto web client.