One of the main points of DI is testability, but the point of using a DI framework is to remove the need to write lots of factory code. That's the reason I use guice it anyway.
Dan. On Mar 25, 2:41 am, "Dhanji R. Prasanna" <[email protected]> wrote: > On Wed, Mar 25, 2009 at 12:41 PM, Brian Pontarelli > <[email protected]>wrote: > > > Someone still has to create the classes and wire everything together. > > Duck-typing doesn't really help or hurt. > > That's no pain at all since everything is mockable in Ruby without > interfaces or constructor separation. You can even redefine classes on the > fly for test cases. The main point of dependency injection is testability, > the rest is... well, nice, but not really germane to the the design pattern. > > Dhanji. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
