Frameworks: Whats good about them, whats bad about them.
Frameworks: Whats good about them, whats bad about them.
In my years programming, I've always advocated the use of frame works. While I have only every really used a handful of them myself, (across CF,PHP and Flex) there are underlying principles around frameworks that really appeal to me.
But there are things about using frameworks you need to keep in mind.
But first, some of the good things (a non-complete list):
1. Most frame works have the MVC paradigm at their heart. This is GOOD
2. Force some degree of fore-thought before launching in to code
3. If you use a documented framework consistently, handing over of projects is simpler. (key word "documented"! )
4. Enforces a structure to your code base, which, once you understand it, *usually* means you can de-bug it better
Now the bad things (also a non-complete list):
1. You are trusting code you may not fully know, or even blindly trusting this code.
2. Frameworks are not "silver bullets" that make you problems go away.
3. "Roll your own" frameworks are often badly documented, so hand over can be a real nightmare
4. You can get (feel?) trapped in a framework if it starts to fail you in anyway
5. There is no "perfect" framework. All have pros and cons. You'll need to find them and work with them.
I used to say "The more something does for you, the less you can do with it". Of the past 5 or so years, this statement is less and less true, as there are some very comprehensive frameworks out there that do a very good job of empowering you to do what you need to do, while doing a lot of under-the-hood stuff too.
To expound on a couple of the "Bad things"
While trusting code you don't "know" isn't always bad, it is bad if you start having issues with it. You are faced with some options.
- Abandon it
- Dig in to it and "learn" it so you can fix it
- Work round it's limitations
While I like using frameworks where I can, there is always the "can-o-worms" fear that maybe framework "ABC" or "XYZ" isn't quite a clever as I was expecting under the hood...
On the non-silver bullets of frameworks: sometimes it seems (particularly in the "Which framework is king" flame wars discussions), that people are looking for a framework to make all the hard work go away.
Unfortunately this isn't what frameworks are for or about. Which ever framework you pick, you will have to learn how it works.
You will be slower with it than not using it at first. You will be faced with learning the framework AND solving the problem(s) you are developing to.
But...
- the more you use it, the faster you will get at it
- When faced with problems, you'll know how to solve them within the framework, so you time isn't eaten up with "what goes where", but you can focus on the problem at hand.
While the above is by no means complete, I had to let it out somewhere! Thanks for listening!
PS: I have nothing but absolute respect and props for the men and women who give up so much of their (usually personal) time to create/code and manage any framework! My hat is off to them!
PPS: One other thought: A lot of what I've said above is also true for application platforms too!
