News for hackers. Stuff that matters.

A comment on Django vs. Flask for a long-term project. Parent comment

Re:Django vs. Flask for a long-term project by TylerE on Wednesday January 22, 2014 @05:05PM (#7105695)
The other counter argument: You have features, A, B, and C. FullStack Framework 1 provides A+B+C, Lightweight Framework 2 Provides A+C, Lightweight Framework 2 provides A+B, minimalist Framework 4 provides B only. Are you better off learning (and keeping in your head) framework 1 only, or 3 smaller frameworks, which still doesn't cover the C+B case.
[ Parent | on HN ]
Re:Django vs. Flask for a long-term project by collyw on Monday February 03, 2014 @07:54AM (#7170354)
I would say that learning the full framework also has the advantages, that

A) It works together. The framework is a framework as a whole, so you can expect all the components to work together, without having to fudge things, or crate workaround for things that don't want to play nicely together.

B) There should be some consistency in the components and the way they are used. That should theoretically lower the cognitive load, if that's the "bloated" that people are complaining about.

[ Parent | on HN ]