On Sunday, July 29, 2012 1:22:49 PM UTC-4, Alan Gutierrez wrote: > 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. >
That's an interesting and thoughtful take on dependency injection. And for the uses Node is put to, it is likely usually to be true. I think there is another element to it, though: The fork-it model only really works when - The dependencies are packaged inside the software - The software is a static bundle of code and you replace the whole thing, not update parts - It does not do any dynamic loading of stuff not packaged with it - aka any sort of *runtime* "plugin" architecture in other words, as soon as you have dynamic code-loading, or customers assembling custom distributions, if you want to give as close to the guarantee of reliability you could offer if you packaged it all yourself, you're back in interface-land. Those things aren't generally issues if you're deploying a webapp you wrote on servers you control, and are more common for desktop software, but they are things that, as a framework matures, people tend to start trying to do. -Tim -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
