Actually, this gonna be asked in a variety of programming interviews as well. Many time people try to just understand what is a library and then try to understand what is a framework. We need to understand both things side by side. When we try to find out definitions for both things, we can find quite a common definition which is a collection of library is a framework. This can be true or cannot be always true. So we need to understand both sides by side.
Here I take two examples ;
First Example:
Library and framework, both of them are dependent on the rule. One is your home and another one is just like your school or your university. We make an analogy here that your school is your framework and your home is just like your library. The point is when you have less number of rules, it is more likely that it is going to be possibly a library and when there are a number of rules then there are higher chances that it's going to be a framework. For example, in our home, we just throw off our t-shirts wherever you like. but when we go to school or university, there are fixed places where we put our bags. Like that, in school, we are bounded by more rules while on the other hand at home, there is less number of rules.
So the library is moreover like our home, it's like whatever I want to do, I'm gonna be doing it and similarly on the framework, it is more bounded by the rules that we are only bounded to do certain kind of things.
Second Example:
The second example is moreover code-oriented and the people who are associated with even little bit kind of the code even like simple Javascript or jQuery will be able to understand it. In a simple library, a collection of codes, some functions or all these such things are being packed together and is being used over and over, that's basically our library now. The difference here is in a library we are making a call to a library, but in the framework, we are calling to our code.
No comments:
Post a Comment