Tech Embassy

Monday, May 22, 2006

Library vs. Framework

A framework is more than a library, and actually maybe has nothing to do with a library.

Here is an interesting article on Martin Fowler's blog about Inversion of control, but in the article, Martin discuss the difference between the library and the framework, as well he refers to another article about frameworks.
I can summarize the points in both articles in the following:

A library is about reusable functionalities, but a framework is about reusable behaviors.
A library is something you call/inherit from your code, but framework is something that calls your code or provide services for your code.
A library is a collection of components and classes, where framwork is how abstract classes and components interact with each others.

I can explain the framework by this definition:
Framework is an abstract design that embodies how the application works, and it has "hooks" where you can "inject" your module, or component.


  • It's not really fair to say frameworks and libraries have nothing to do with each other. It's kind of like saying penis and vagina have nothing to do with each other. A framework is like a breadboard where you can insert electronic components. A library is a set of components.

    By Anonymous Anonymous, at 3:34 PM  

Post a Comment

<< Home