Comments on: The lesser of two evils? http://blog.amnuts.com/2007/12/17/the-lesser-of-two-evils/ php projects, javascript, and... stuff. Wed, 20 Aug 2008 14:37:57 +0000 http://wordpress.org/?v=2.5.1 By: Andy http://blog.amnuts.com/2007/12/17/the-lesser-of-two-evils/#comment-23 Andy Tue, 18 Dec 2007 14:55:33 +0000 http://blog.amnuts.com/2007/12/17/the-lesser-of-two-evils/#comment-23 Thanks for your thoughts, elazar! Using an existing framework would be a good step in the right direction is applications need to be written from scratch... Of course, there could be (and already have been on the 'net) huge debates around which one to use; ZF, Symphony, Prado, Cake, etc. But I suppose, as with anything, you'd use whatever one serves your purpose. (At work and home I've opted for ZF.) Thanks for your thoughts, elazar!

Using an existing framework would be a good step in the right direction is applications need to be written from scratch… Of course, there could be (and already have been on the ‘net) huge debates around which one to use; ZF, Symphony, Prado, Cake, etc. But I suppose, as with anything, you’d use whatever one serves your purpose. (At work and home I’ve opted for ZF.)

]]> By: elazar http://blog.amnuts.com/2007/12/17/the-lesser-of-two-evils/#comment-22 elazar Tue, 18 Dec 2007 03:59:07 +0000 http://blog.amnuts.com/2007/12/17/the-lesser-of-two-evils/#comment-22 I think this situation is part of the reason why frameworks and libraries seem to be coming out of the woodworks in alarming numbers. It's all too often that existing applications have a lot of extraneous features or aren't easy to extend or integrate with. Outside of the options of using third-party software or rolling your own, a third option is to use an existing framework or library that handles the lower-level operations and leaves you free to code the higher-level or more advanced application features. An additional advantage to doing this is that the applications and frameworks can become established and widely-used, making your experience all the more valuable and portable between projects and even jobs. If you're looking at a particular project now, take a look at any of the MVC frameworks out there, libraries like PEAR or PECL, and see what's there already that might do at least a significant amount of the lower-level work for you. It may also help to open source for your core and get the related community involved to help in its development so all the work isn't on your shoulders. That's my $0.02. I think this situation is part of the reason why frameworks and libraries seem to be coming out of the woodworks in alarming numbers. It’s all too often that existing applications have a lot of extraneous features or aren’t easy to extend or integrate with.

Outside of the options of using third-party software or rolling your own, a third option is to use an existing framework or library that handles the lower-level operations and leaves you free to code the higher-level or more advanced application features. An additional advantage to doing this is that the applications and frameworks can become established and widely-used, making your experience all the more valuable and portable between projects and even jobs.

If you’re looking at a particular project now, take a look at any of the MVC frameworks out there, libraries like PEAR or PECL, and see what’s there already that might do at least a significant amount of the lower-level work for you. It may also help to open source for your core and get the related community involved to help in its development so all the work isn’t on your shoulders.

That’s my $0.02.

]]>