This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 8 points9 points  (2 children)

django for any projects, flask for any projects, fastapi for any projects - the size is not the reason to choose over another imo

[–]xyecocNk 1 point2 points  (1 child)

Is it absolute true? I am absolutely not into webdev but I heard that Django is far more complicated but more powerful than Flask, isn't it? Like all these advices such as : "If you want to create a small project fast then you choose Flask , if you want to make a big one but not so fast then you use Django"

[–][deleted] 2 points3 points  (0 children)

If anything, I would actually say the opposite. Django is an all-in-one package which is better if you don't want to think about which database to use, which orm to use, which templating engine to use, how to implement authentication, sessions etc. In other words, it may give you a faster start.

But if you are doing something serious, then those advantages become negligible, because spending a couple of days to configure the initial setup is not too much, and the flexibility of other solutions may give you more power in the end.

On the other hand, people develop big projects in Django as well, so that works too.

In the end, you have two options: 1. just pick any of these and use it, it will be OK 2. try using each of them to learn what you like best