>LightWire is simpler if you want to know HOW a DI engine works, >the core code in LightWire is under 400 lines so it is a great way >to look under the hood and really get the pattern
That's a plus. Personally, I like knowing _how_ things work, not just that they _do_ work. Makes it easier to understand the capabilities (and limitations) of a given tool and of course change or fix things as needed. (Not that anything ever changes in an application ;) >I don't know about anyone else, but it leaves my mind free to concentrate on >getting the job done, instead of thinking about architecture issues all the >time and wondering if i'm doing it the right way or setting myself up to get >stuck in some corner down the line. Well put. That was my biggest concern about committing to a framework. Knowing so little about them, I didn't want to paint myself into a corner by choosing the wrong framework or something that was not well suited to the task at hand. > It wasn't until i just tried it, following a few examples, that it became > suddenly really simple to understand, and very useful. Thanks for all of the comments. Time to dive in. I'm going to run some simple examples with ColdSpring, Transfer and Lightwire and see if a lightbulb goes off. I'm sure I'll be back later with more questions :) -- --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
