Hi. I have another naive question. Nathan has been helping me out == a lot == with node-gyp and node-bindings and I want to say publicly that these tools are going to be ++huge for those of us forced work in platform-heterogeneous networks.
One thing I notice is that node-bindings seems designed to support the pattern of installing a separate copy of each required module with the requiring node app. This practice of multiple copies makes (made) a certain amount of sense before node-bindings, because it provides one way to ensure the version, platform and architecture of modules match the requiring app. But now (when) node-bindings does that. So what are the remaining reasons to keep multiple copies of modules instead of just installing globally shared copies (which could still be segregated by platform)? (I have not studied the JavaScript runtime model, so if you tell me that two apps requiring the same file implies some shared state I would not be surprised.) I'd like to start to understand this better, because I see benefit (quantifiable in dollars) to maintaining one copy of each module per machine instead of one copy per app per machine. Thanks for cluing the noob. -- 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
