First things, what is a framework? It actually depends on the context it is used. It can be defined as an abstraction tool that makes it easier to develop applications and reuse code. A framework assures you with the certainty that you are developing an application that is in full compliance with the professional rules, that is organized, and that is both maintainable and upgradable.
Many times, you should ask yourself, why you need to do the same thing every day when there’s a new bridge to shorten the path. Think of web frameworks as bridges that will help you code faster and easier.
Faster, as it permits developers to save time by re-using generic modules in order to focus on other areas.
Benefit of framework not ends here, developer basically spend 2 or 4 days creating an authentication form. The time that is saved can be devoted to more priority components as well as to the corresponding unit tests; giving you solid, sustainable and high-quality code.
This is exactly the basic principle of a framework: Not having to reinvent the wheel.
Less time coding — we became so efficient we just put ourselves out of a job.
It doesn’t take a mastermind to figure out that using a framework saves you stacks of time and effort.
At RLInfocomm, we use PHP frameworks like CakePHP, CodeIgniter and the Zend Framework which provide a rock-hard structure for our code, it also offers some extra functionality that would be much harder to replicate on its own. It’s important to note, too, the frameworks mentioned follow the MVC pattern, which is fairly common.
— by Robin