Re:Django vs. Flask for a long-term project
by elbear on Wednesday January 22, 2014 @05:30PM
(#7105836)
I think that he meant that Django has a bigger ecosystem with a lot of different apps, so you don't write everything from scratch. There are apps for migrations, building a REST api, having a tagging system, integration with search engines and many others. I won't comment on the state of the Flask ecosystem, because I don't know it, but I imagine it's smaller.
[ Parent
| on HN ]
Re:Django vs. Flask for a long-term project
by poulsbohemian on Thursday January 23, 2014 @12:20PM
(#7109506)
Here's the reality though: so many of those apps in the ecosystem are half-baked, unsupported, and don't actually work. It's a mess trying to match existing code to a set of customer requirements, all the time with the customer saying "Can't you just use django-foo?" ignoring the fact that django-foo was last upgraded 5 years ago and won't work with anything newer than django 1.4, and doesn't do half the things in their requirements anyway. It's pretty rare that any of those applications in the ecosystem actually save me any time.
Re:Django vs. Flask for a long-term project
by elbear on Friday January 24, 2014 @10:54AM
(#7115464)
There are plenty which are production ready and good quality. Some examples that I use are haystack, compressor and rest-framework. If the customer tells you to use a shitty app, explain to them why you can't. They don't know better. You're the expert.