Frameworks are all the rage these days. If someone says lets build a web application there is usually a developer nearby saying let's use a framework to build that. Sure, there are times when using a framework isn't the way to go. But, for 99% of the new web applications that need to be built there are great benefits from using a framework. Let's take a look at 7 of them.
Save Time
Do you code your own OS? Do you create your own programming language? You use the work of others to help you build applications faster. That's what frameworks do. They do a lot of the heavy lifting for you.
Build Like An Expert
Chances are you are not an expert at all of the tools you need to build a web application. There is the programming language, javascript, and your database of choice as a start. If you use a framework you can have an expert built system with expert built methods. For any non-expert this is a definite bonus.
Don't Reinvent the Wheel
Why try to rewrite what has already been done. When I was taking my first college programming course one of the things my professor taught us was to use someone else's work if it was good. To not reinvent the wheel. Frameworks are the wheel. Why would you try to reinvent it. Especially if it was built by an expert.
Templating
Frameworks are going to use a software architecture like MVC or PAC which have a great separation between the logic and the presentation layers. This means that if you want to update your interface (e.g., you are making usability updates) or you are integrating web services (e.g., SOAP, REST, etc.) your presentation doesn't cause you to rewrite parts of your business logic.
Fixing Bugs
Anytime you build a complex software system there are bugs. Even if your bug reporting tool says there are no bugs they are sure to exist. That's why bugzilla reports "zarro boogs found" when you have none reported in your tool. It's a bug to say that just like there are still bugs in your tool. Isn't it better to have a base system that has hundreds or thousands of eyes finding and fixing these bugs so you don't have to.
Become A Better Programmer
When you work with a system that was developed by experts it helps you become a better developer. You learn from what has been done for you. You see how they did it and you learn new ways to develop yourself.
Test Driven Development
Web application frameworks typically have test suites built in. This allows a developer to test their work as they go. They provide the groundwork for test-driven development.
This is my handful of reasons to use a web application framework. Unless someone has a good reason I recommend using a framework. What are your reasons to use a web application framework?
Nicely done
Great article! "K.I.S.S." and "don't reinvent the wheel" are rules I live by everyday.
Any favorete web framework
Any favorete web framework (php) ?
Drupal
My framework of choice is drupal. If I need a framework that isn't a full stack framework I'll go with Zend.
This is just my personal choice. I'd recommend going with these or RoR, django, Symfony, or many of the other frameworks available before writing your own system.
sub-frameworks
you mentioned Drupal which would be a broad system framework, do you use a sub-framework like a CSS framework? like perhaps the zen theme? or do you choose a drupal css theme template based on the specific project needs?
Home Grown
On most of the sites I work on Bob does the design and lays out the groundwork for the theme. But, I do on a semi-regular basis (once every couple or few months) pump out a design. For those I write custom CSS. My last 4 projects have been so radically different that there is no base CSS framework that would cover them.