Author here. I know this could be a shock, but I can do almost anything with a mega-framework, too.
Using a mega-framework there could be a point where I would have to work around the limitations while using a micro-framework just means that there could be the point that I invest time (implementing, maintaining, maybe even some troubles updating parts of the system to new versions,...) implementing something that a mega-framework provides out of the box.
For the sake of fun I wrote a basic implementation using Django and PostgreSQL and one using Flask and Redis. I did not use a stopwatch but I would say that it took the same amount of time.
The only difference? In my experience I will have an easier time adding a feature quickly thanks to all the batteries Django already includes.
I have build sites and services in both of them. I am definitely more familiar with Django. But using flask-batteries is just more work / LoC to use them. Building a feature without batteries is IMO nearly the same in time and LoC.
Of course you are more flexible and have a smaller default installation, which are great things, but most of the time Djangos batteries "just work" and every hour I can safe working on a project and still delivering the expected results is great for me and my clients.
Using a mega-framework there could be a point where I would have to work around the limitations while using a micro-framework just means that there could be the point that I invest time (implementing, maintaining, maybe even some troubles updating parts of the system to new versions,...) implementing something that a mega-framework provides out of the box.
For the sake of fun I wrote a basic implementation using Django and PostgreSQL and one using Flask and Redis. I did not use a stopwatch but I would say that it took the same amount of time.
The only difference? In my experience I will have an easier time adding a feature quickly thanks to all the batteries Django already includes.