3 ms·
Interesting take on this. And I respectfully disagree. I would use Pyramid over Django any day of the week, and Flask for anything smaller. My reasoning is tha
by ianamartin 10y ago
Interesting take on this. And I respectfully disagree. I would use Pyramid over Django any day of the week, and Flask for anything smaller.
My reasoning is that any project that needs as much as Django has built-in is going to need the custom work you put into a Pyramid project anyway, so you might as well start off there and use a nicer API from the get-go. Anything less is Flask territory from my point of view.
- gshulegaard 10y agoAnother interesting point of view. So I thought I would throw in my two cents on this. I started web development using Django, then tried Pyramid, and finally moved on to Flask. And since picking up Flask, I haven't gone back...and I wouldn't go back to "heavier" frameworks...although I have considered taking a peak at a couple other micro-frameworks. I have a couple strong (personal) reasons for this (read: YMMV), but the biggest thing for me is I see web development moving towards a strict separation between front-end and back-end (SPA's, web assembly, microservices, etc.) as well as multi-model/multi-storage. Neither of which lend itself well to all-inclusive framework solutions IMO. At the end of the day I guess the take away is to remember that it's great to have so many strong frameworks each with its own strengths to choose from in the Python ecosystem.