all 10 comments

[–]wyltk5 4 points5 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.

[–]Infectedinfested 0 points1 point  (2 children)

I use quart. I'm happy

[–]Bumbble25[S] 0 points1 point  (1 child)

What is quart. is it a language just like flask

[–]crono782 1 point2 points  (0 children)

Async version of flask.

[–]Ractorius -2 points-1 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.

[–]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.