There's a good question, and it was recently elaborated upon by my buddy, dave in this post.
Mach II came to life out of fusebox. My understanding is there was a divide in the fusebox community, some people wanting to utilize a procedural framework, and some people wanting to go an object oriented structure. If anyone can elaborate, please I'd like to hear the history.
So what is a framework?
A definition I've come across is that a framework is a class library that captures patterns of interaction between objects. A framework consists of a suite of concrete and abstract classes, explicitly designed to be used together. Applications are developed froma a framework by completion of the implementation of abstract classes. A framework can be also utilized to include additional utilities to aid in the completion of end-user applications.
So if we agree this defines a framework, what is a methodology?
A methodology is a codified set of recommended practices. I think that summarizes it up.
So what is Mach II. Well Mach II is definitely a framework, but utilizing that framework based software development, is a methodology. Utilizing a framework brings a different approach to solving a problem. One works from within the constraints of the framework, because the framework is extended for multiple applications.
So the code of Mach II itself is a framework, but utilizing Mach II in application development is a methodology.
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
1 Comments to “Mach II: framework or methodology”
I'm thinkin of waiting until 3.0 ... after adding the mt-blacklist plugin to kill off commentspam .. things seem stable, and I haven't had any trouble with the xml-rpc bug that they describe.



