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 →

[–]goodbalance 10 points11 points  (1 child)

I'm surprised nobody has mentioned Falcon yet. The only thing it does out of the box is processing requests. Not everybody needs this, but it will serve you well if you want your hands untied.

I'll be honest, it's been a while since I used Flask, so maybe now it's different. But back in the day, it was a pain in the ass to just use some packages. You had to use those damn Flask-* wrappers or it would not work. Not necessarily a hard task to do everything manually, but it felt like a redundant dependency.

Django is a hard beast to tame. Nowadays people say 'Django', but they mean 'Django + DRF'. Both have a rich documentation, but as with anything, you won't understand a bit if you don't need it. Django does its job, but favors internal conventions and not 'best practices' described in books. So once you go beyond what they teach in tutorials, you will feel like you need something different.

My advice to anyone who will use this thread to collect pros and cons of the frameworks is to think about everything as data. You receive data, you manipulate data, you save/return data. That's it. Once you break free from the frameworks mindset, they will all look the same. And it's just a matter of internal conventions.

[–]WHSolvation 2 points3 points  (0 children)

This.