5 ms·
Fully developed Flask projects tend to be significantly more hairballish and custom compared to something like Django, but it's extremely hard to kick the habit
by dmw_ng 4y ago
Fully developed Flask projects tend to be significantly more hairballish and custom compared to something like Django, but it's extremely hard to kick the habit and convenience once something has initially been prototyped in Flask (or Bottle, same deal). Commercially I'd much rather encounter an existing Django project, but at home 90% of the time I'll reach for Flask first, the rest being cases where there are some off-the-shelf Django components that will definitely save a ton of time, and the ceremony is worth paying.
- aenis 4y agoI am not sure if thats so hard. I had a commercial app based on Flask, about 20 endpoints and 1MB of source code, and it took me a whole 1 day to port it to FastAPI. IMHO Flask is quite elegant if used properly.
- Spivak 4y agoFlask is tight and elegant, the parents point is that unlike Django which is far more batteries included that large Flask projects end up half implementing Django but worse. And it’s no dig on Flask specifically, you can play this game with Django too, large Django projects end up half implementing ActiveJob and ActiveSupport but worse.
- jtdev 4y ago
- guggle 4y agoI've been doing similar projects (ecommerce apps) with both Django and Flask. I would choose Django over Flask anytime. MUch less fiddling.
- danjac 4y agoI've seen enough "hairball" Django projects in my time. That's not to knock either Flask or Django (or FastAPI for that matter), they all have their strengths and weaknesses, but there is little defence against a developer determined to avoid best practices and reading the documentation even for a framework as mature and well-documented as Django.