At Sun, 13 Jul 2014 09:26:38 +0200, Vincent Bernat wrote: > > ❦ 12 juillet 2014 23:08 +0100, Steve McIntyre <st...@einval.com> : > > > And I've got to ask: for the couple of trivial examples that Frederick > > pointed out - why on earth do these even exist as libraries instead of > > being inlined wherever they're needed? > > Because, in node, a library is cheap and the functionality get unit > tested. That's why there are so many dependencies in this ecosystem.
You have all the extra metadata, extra git repository, extra dependency tracking, etc. no matter how 'cheap' a library is. And as far as I understand npm (correct me if I'm wrong, I don't use npm very often), it will install dependencies in a nested way, so if app1 use library1 and library2, and both those libraries use tinylibrary1, tinylibrary2 and tinylibrary3, then those 3 tiny libraries will be installed both under library1 and library2. I wouldn't really call that cheap. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87wqbhy54i.wl%jer...@dekkers.ch
