Web Frameworks
This was my last in a string of posts in a discussion on Clear Function's weblog:
I was thinking about frameworks this morning as I was reviewing some of the above links (and a few others). I am currently working in Plone (ZMI), which is a python framework. Once I got the hang of a few things it wasn’t too bad — however, there are still the unexpected things that I don’t really know where to begin in solving an issue. It takes time. Time is money. Personally, the concept of a framework is great, but I would still want to build something myself (or with a group of developers) where we know the ins/outs of the entire framework and know how to control what.
I found this article on why frameworks suck that presents a lot of valid points. In some instances, it really is like learning a whole new language — because a framework is a new layer on top of the programming language (handling common used functions and eliminating redundancy, etc).
I am currently building a custom framework for our new website (and sister sites). I want something that will work across several domains — creating a set of commonly used classes into a global framework. Since I am the one building it, its much easier to expand and troubleshoot.
I am not against frameworks — I just feel that you still have to learn the framework (which in some cases could take the same time to learn an actual language). Just another view on frameworks and their implementation.
Thoughts?
2 Comments Add your comment
Stephen December 12th, 2005
I think it really depends on your needs. There are benefits to both. There is also negatives to each one.
If you go with a framework that is already available there is already support, documentation and a community.
Learning some frameworks is like learning a new language, but I would venture to say some of them are easier than others. There are a lot of frameworks out there that try to do too much and become very messy. The Rails and the Djano projects seem to be very clean implentations done by very smart people.
Sometimes building a framework can be an extremely tall order. A lot of times there isn't time and resources to do this. And if you go this route are you making it just as hard or harder for someone else to pick up and learn.
Sometimes you need your own framework simply because the project needs demand it.
Just some thoughts...
Nate Klaiber December 12th, 2005
Yeah, the big thing is fitting your needs. There are some great frameworks out there, but if they dont really meet my needs - or give me options I will never need/use (but dont have what I need) - then I need to develop my own framework.
I am currently doing this with the new Barbour Publishing website, where I am connecting it to several other 'micro-sites' and tying it all in with a single logon. There are many pieces that will be shared throughout all sites (database, styles, classes, etc) - and they will be used in custom fashions on each site.
The big thing I am noticing right now: TIME. There are so many things I want to do/implement - but there is only one of me. This is where some 'frameworks' might help with certain pieces. While building our current framework, I am doing my best to comment as best I can for other developers who may have a hand in it. This can all be exported to phpdocumentor for others to read and interpret. BUT, I have no documentation on it as of yet - so that may be a next step. Having the support and documentation up front is a bonus.