On Fri, Jul 27, 2012 at 10:25:53PM -0700, mixu wrote: > I've never really needed to dependency inject into third party modules. If I > did, I'd rather fork the third party dependency than do some sort of dynamic > solution.
That's part of what has changed with development since the rise of `git` and `GitHub`. IoC tries to address the complexity of project lifecycles using design patterns, but these days we tend to that through communication; issues and pull requests. The ability to get a patch into the source has given programmers more confidence in their dependenies. They are no longer deferring decisions by "programming to interfaces", but instead making a commitment to a dependency. C# and Java are afraid of commitment, they see it as a potential hostage situation. -- Alan Gutierrez - http://github.com/bigeasy - http://twitter.com/bigeasy -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
