News Feed
Jobs Feed
Sections




News Archive
php|architect Blog:
To use a framework, or not to that is the question
April 05, 2010 @ 10:05:20

On the php|architect blog there's a recent post from Jayesh Wadhwani asking a question developers all over the world wonder every day - to use a framework or not to (and what's the benefit)?

A framework is usually thought of or defined as an underlying structure. You could imagine a wooden structure, sort of a skeleton when a house is being built. This provides a guide, structure and flow to build the house. A programming framework pretty much does the same thing. A programming framework provides for a structured and disciplined programming which results in a more consistent output from a programming team.

He talks more about some of the things that come with framework use like the utility and "housekeeping" code as well as code you know has been tested and used by other projects successfully (especially with something like the Zend Framework. Remember, though, there's bad that comes with them - a possible steep learning curve and overhead that could be caused by using the tools it gives you badly.

0 comments voice your opinion now!
framework use opinion pro con


blog comments powered by Disqus

Similar Posts

Marco Tabini's Blog: Thoughts for a new year: PHP as the new Java

Community News: Symfony Framework Makes Some Updates (v.0.6.2 and Content)

The Bakery: Keeping bindModel and unbindModel out of your Controllers

Ivo Jansch\'s Blog: What php search engine would you use?

NETTUTS.com: Introduction to the Smarty Templating Framework


Community Events











Don't see your event here?
Let us know!


example podcast release composer tool code functional series language development object conference testing zendframework2 framework unittest introduction community interview opinion

All content copyright, 2013 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework