From: Tony Arcieri Date: 2012-02-08T16:36:29+09:00 Subject: Re: [ANN] DCI v0.1.0 released --0015175900420d354504b86ef436 Content-Type: text/plain; charset=ISO-8859-1 Okay, never mind me, I'm just a little drunk and got DCI confused with DI. My bad ;) On Tue, Feb 7, 2012 at 10:19 PM, Tony Arcieri wrote: > Hi there, > > I have a question... what problems does dependency injection solve that > duck typing does not? > > As Rubyists we can compose in such a way that we expect objects which > quack a certain protocol. The method protocol in use becomes a kind of > abstraction, allowing us to swap in other types of objects which quack the > same, but may be completely different objects of a completely different > class with a completely different implementation. > > Dependency injection seems like myriad complexity in order to solve a > problem that Ruby already solves by the very nature of its type system. I > have used this sort of approach to simply compose the kinds of systems I > can't fathom being able to build in statically typed languages. > > So all that said, what does dependency injection offer Rubyists that duck > typing does not? > > On Tue, Feb 7, 2012 at 8:02 AM, wrote: > >> DCI 0.1.0 has been released. >> >> Faithful DCI framework for Ruby application development. >> >> * home: https://rubyworks.github.com/dci >> * code: https://github.com/rubyworks/dci >> * mail: http://groups.google.com/groups/rubyworks-mailinglist >> >> This is the initial working version of DCI. >> >> Changes: >> >> * Happy Birthday! >> >> > > > -- > Tony Arcieri > > -- Tony Arcieri --0015175900420d354504b86ef436--