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.
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.
Bloated also tends to mean things like "takes up way too much conceptual space". Which is a valid argument against a lot of frameworks. The idea being: i have to learn to think about the problem in the framework's way, and restructure my solution around it.
The opposite being: with micro-frameworks I can just wrap my app with the framework and get some functionality out of it that would otherwise be difficult or boiler-plate.
(The counter-counter being: then you end up having to reimplement a buggy version of a full framework anyway as requirements grow and change...)
The real solution is to not think of it as either/or , but as "both, sometimes".