From: Intransition Date: 2012-02-09T00:43:52+09:00 Subject: Re: [ANN] DCI v0.1.0 released ------=_Part_164_6005175.1328715830290 Content-Type: multipart/alternative; boundary="----=_Part_165_30813166.1328715830290" ------=_Part_165_30813166.1328715830290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, in implementing this it struck me that DCI is kind of like DI taken to then next level of abstraction. So your question isn't really that out of place --to which I would say, you are right. DI really doesn't fit Ruby, but DCI does bring something more to the table in the way it makes you think about and implement you problem set. Actually, I'm not sure DCI is all that great an idea. That remains to be seen. My goal here was just to create a fairy solid implementation of the concept (I'd say I'm 80% of the way there at this point), so that people could at least give it a try/use it as a reference. ------=_Part_165_30813166.1328715830290 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, in implementing this it struck me that DCI is kind of like DI taken to then next level of abstraction. So your question isn't really that out of place --to which I would say, you are right. DI really doesn't fit Ruby, but DCI does bring something more to the table in the way it makes you think about and implement you problem set.

Actually, I'm not sure DCI is all that great an idea. That remains to be seen. My goal here was just to create a fairy solid implementation of the concept (I'd say I'm 80% of the way there at this point), so that people could at least give it a try/use it as a reference.


------=_Part_165_30813166.1328715830290-- ------=_Part_164_6005175.1328715830290--