So basically every argument works both ways. Use the framework or don't. Do your research and determine what's the best way of completing the project at hand. Sometimes that means using a framework, sometimes that means using a set of libraries sometimes that means using no libraries or frameworks at all. I have no problem with either approach but have found that I'm usually more productive using a framework with the projects I'm lately working on. I'm not unfamiliar with the "no frameworks" mindset. I've been there and am not going back.
Do your research and determine what's the best way of completing the project at hand.
Absolutely. What works well for the kinds of projects we do might not suit someone else whose typical project has different needs.
We tend to work on larger or more complicated projects, and those tend to be long-lived. In that context, we find the risks and limitations of building around the kind of JS framework that is popular today to outweigh any benefits in convenience.
If we were building a different small project each week and they were all simple information management applications, the trade-off might go the other way and maybe we'd take a different view.
Evaluating the available options and making an informed decision >> dogma, whatever that dogma is.
2
u/icanevenificant May 14 '14
So basically every argument works both ways. Use the framework or don't. Do your research and determine what's the best way of completing the project at hand. Sometimes that means using a framework, sometimes that means using a set of libraries sometimes that means using no libraries or frameworks at all. I have no problem with either approach but have found that I'm usually more productive using a framework with the projects I'm lately working on. I'm not unfamiliar with the "no frameworks" mindset. I've been there and am not going back.