+ 3
What is the negative side of frameworks?
is there any moment that is not good for using a framework?
2 Answers
+ 9
I'd say there are two relevant cases (i was thinking about the third one but i forgot it, sry)
1) The framework is slowing your application, too much. At this point ask yourself: "I really need all the features of this framework?" and in most cases the answer might be: "No, i don't". Now it's time to choose whether remove the framework from your project or just use some portion of it that you need to speed up your development process.
2) The framework is hard to grasp, very hard to grasp. I have to admit that i had the same problem with Laravel (now i chosen to give it a second chance), a framework should be easy to learn, you don't want to spend weeks reading the documentation, the framework should speed up your development process. At this point it would be like learn a new language, ask yourself: "It worth?"
Conclusion -
In most of the cases, at least in web development, you are going to use frameworks, learn a new framework is always exciting (except for me) and you will adapt your mind at different ways to code, however there are few questions you may want to ask yourself before to start a project:
1) Are performances a priority?
2) Your project is a small one or a big one?
3) Do you like anime?
4) Is the framework stable in terms of development team (eg. Angular: Google, Bootstrap: Twitter, etc) and docs?
Hope i was clear enough.
+ 3
Yes, I understand that there are projects that do not require such frameworks because of their size. 3) Do you like anime? kkkk Ok, thank you.