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

Project: Warden: A user database authorization package for FuelPHP

Zend Developer Zone: Zend and IBM Post QEDWiki Screencast

Padraic Brady's Blog: Zend Framework Community Review Team

Community News: CakeFest 2008 Announced (and a Call for Papers)

ServerGrove Blog: Why Symfony2 already rocks


Community Events









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


community composer framework zendframework2 opinion phpunit podcast interview tool example object introduction unittest development testing release api database language code

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