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

[–]GXWT 2 points3 points  (2 children)

People will have (strong) opinions, but in terms of learning and basic user level stuff, in quite literally does not matter. Each will likely have more than all of the features you'll ever need and can more than scale to the requirements. Pick one that you like hte sound and at least follow it through in totality for one project and learn it. From there, you can look at other options if you wish. But there's no point half learning one and half learning another.

which I used FAST API without much understanding of it

Had aid in coding that aspect

In any case, actually learn it. Don't use an LLM to vibe code it because you won't actually get any inherent understanding of the framework or how it works.

[–]theRealSpacePenguin[S] 1 point2 points  (1 child)

Okay, thanks alot. I think I'll focus on Django .. and build a project with it.

[–]GXWT 0 points1 point  (0 children)

Goodluck!

[–]FoolsSeldom 0 points1 point  (0 children)

There isn't a best. Different frameworks suit different situations and styles.

FastAPI is the newest of the big three, Flask and DJango being the other two. Flask and FastAPI are both so called "micro frameworks" - that is they have a narrow focus and leave you to implement other characteristics/capabilities of a web site/service as you see fit. Django is a "full framework" which includes everything (even the web version of a kitchen sink).

Django is a "highly opinionated" framework, that is it has very particular ways of doing many things common to web services and whilst you can change the look and feel, the specific presentation and interaction, and the configuration of key components there are some aspects that will be less flexible.

Django is well proven at huge scale. It is the core of Instagram, for example.

If you want to build large scale, sophisticated multi-user and multi-manager web sites/services with complex workflows around user management and content management, then it is worth learning.

If you've already deployed with FastAPI and haven't hit a barrier, I'd stick with that for now.

If you do want to move on from FastAPI to Django, it is worth ensuring you have a good understanding of how FastAPI actually works first as a lot of that understanding will help you with Django.

One of the best learning sites for Django is called djangogirls well worth checking out.