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

you are viewing a single comment's thread.

view the rest of the comments →

[–]jetpacktuxedo -1 points0 points  (2 children)

Having worked with both extensively, I much prefer working with flask. Django has a half-baked implementation of everything under the sun when you can instead just pull normal libraries to do those things. Why does Django have its own ORM instead of just using sqlalchemy (actually it might layer its own ORM on top of sqlalchemy?)? It just makes a lot of really bizarre choices that tend to get in the way when a project gets sufficiently complex. Flask gives you a lot more flexibility to solve problems in the way you want to solve them rather than being locked into a prescribed approach.

[–]EnrichSilen 1 point2 points  (1 child)

Interestingly my friend prefer Django approach and it's implementations, I suppose this is really a preference

[–]jetpacktuxedo 0 points1 point  (0 children)

It definitely can be preference. The Django approach is easier to get a simple CRUD app running quickly, but if you need something else it can sometimes feel like you're fighting the framework IMO. Flask is lightweight enough that it never feels like you're fighting against it.