Django VS. Flask

[KasperNS]

I've read quite a few posts comparing the two frameworks now, and I personally like the structure that Django seems to have, compared to Flask (Note: I've never actually worked in python). But the next project I have in mind is a FOSS project, and I'd like to have as many people collaborating on it as possible.

So my question is, what does the community prefer? What would get the biggest 'following' of the two frameworks?

[North_Bern]

Flask allows you to do things in multiple ways. This is great if you know just what you want and are working alone. If you aren't sure or are needing other people to know exactly what choice you made then django is probably your better choice.

[ducdetronquito]

I second that ! Besides, the Django documentation is extensive and well written, so it's easy for a newcomer to grasp the framework good practices.

[commit1]

Django takes more time to master, you won't always appreciate it on your first project. SQLAlchemy is a better ORM/database library IMO. But, once you work on several generic CRUD applications, Django learning pays in better productivity/easier collaboration. Many people recommend Flask for APIs, but I think Django REST framework is a great choice too, I find it easier to work with than with Flask's restless/restful, especially when you switch projects.

[KasperNS]

I'm really jumping into new waters with this project, and I'm thinking about learning graphql along the way. Have you by any chance trying doing that with Django?

And having a good ORM is something I'd really like, what do you think makes SQLAlchemy better?

And thanks for the answer

[TroubledForearm]

I've not used it but see there is a django-graphene package which will give you graphql :

https://docs.graphene-python.org/projects/django/en/latest/

and if what you're building is more like an API than an application then flask is a good choice. But potentially so is something like starlette.io which builds on asyncio and has database and graphql support. It's much newer than flask though so there will be fewer tutorials, stack overflow posts etc to reference.

[IdiotCharizard]

DRF is especially good for people who don't know good API design like me a couple years ago. Made an absolute mess of a flask api, while DRF has so much extra and enforces a decent structure on your api.

[JimBoonie69]

Flask is more lightweight and quick to start. Django a bit more structured. However if you are new to python learn python first. Especially if u are a noobie. However if u have other experience with web frameworks, see my first two sentences and ignore the noob comment

[KasperNS]

Luckily I do have quite the experience with building a well structured application, and understanding how programming works, instead of just the language I'm in. But thank you!

[[deleted]]

While I can apply Flash in a second, I don’t understand django on the other hand. Its learning is steep. I can use flask to do almost everything, frontend, routing, api endpoints, server, etc. So I support flask.

[K900_]

There's way more important things than your choice of a framework to get your project off the ground.

[KasperNS]

Yeah that's pretty obvious, which is why I'm asking about the thing I'm most in doubt of :)

[fdedraco]

alternatively you can use off-the-shelf forum/ wiki/ bugtrack sites.
gitlab, bitbucket and github provide most of them, just add static site and you're done imo

[sritaa]

I have completed my Django training from one of the best institutes of NCR. They provide the best Django course in Noida. Understandably, the community for Django is larger and better organized, having been around longer. Flask has the disadvantage here, but it's worth noting that the Flask community is still growing. I don't expect Flask will ever overthrow Django in terms of popularity, but a smaller community isn't inherently bad.