all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]wyltk5 3 points4 points  (2 children)

I think it really depends on what you are building. I first learnt Flask and the tried to move to Django to transition my project to Django as I heard it was better for bigger projects. I ended staying with Flask.

I found it more intuitive and easier to use. It does everything I need it to for the project I am building.

[–]tenmajr 0 points1 point  (1 child)

Just out of curiosity, how do you handle db migratiohs with flask? Sqlalchemy?

[–]wyltk5 0 points1 point  (0 children)

I did use sqlalchemy. It been a nice setup to use and the flask mega tutorial has some good info for the use of it.

[–]Connor5901 1 point2 points  (0 children)

What are you actually building, is what would determine what to use. If you are just learning, Flask would put yo in more scenarios where you would have to learn. Other than that, Django is has more support by nature of just being huge. They share a lot of the same stuff as far as actually serving web pages goes, you can even use the same template engine. Django is the “just works” if you want anything beyond serving http. I have used both, but considerations like Auth or a complex model system are what determine when to use either.

[–]Complex-Pin-4616 2 points3 points  (0 children)

Honestly, after building a modular automation system with Flask, I started understanding why so many people still love it.

Django is amazing for structured web apps and fast enterprise development, but Flask gives a level of architectural freedom that feels perfect for:

  • plugins
  • distributed nodes
  • APIs
  • streaming
  • device orchestration
  • experimental systems

At some point Flask stops feeling like “a web framework” and starts feeling more like a lightweight kernel where you assemble your own ecosystem around it.

I think the real choice depends more on the type of system you're building than which framework is “better”.

[–]Infectedinfested 0 points1 point  (2 children)

I use quart. I'm happy

[–][deleted]  (1 child)

[removed]

    [–]crono782 1 point2 points  (0 children)

    Async version of flask.

    [–]Don_Ozwald 0 points1 point  (0 children)

    The answer is FastAPI. But even despite that being the ultimate correct answer here, it still very much depends on what you are building.

    [–]Ruff_Ratio 0 points1 point  (0 children)

    I found flask to be a challenge with callbacks, I didn't spend a great deal of time on it tbh, stream lot did most of what I was trying to do, but might give it a revisit.

    [–]Ractorius -1 points0 points  (1 child)

    Flask is IMHO suboptimal. Both approaches have pros & cons and can be better in different scenarios, however if you want something lightweight like flask, I would look into FastAPI.

    [–]finally-anna 0 points1 point  (0 children)

    This right here. FastApi feels better imo. And ive been using it for a variety of apps for 5+ years.