In this thread: people starting to get mad about stuff I was mad about 4 years ago.https://reddit.com/r/programming/comments/51974o/the_cost_of_small_modules_in_the_javascript/ …
-
-
rust also has a small-modules bias, but I tried to learn from npm and make cargo *good* at small modules.
-
Is the goodness mostly due to Rust compiler optimizations or is there something inherent in Cargo as well?
-
I cover it somewhat here. https://blog.rust-lang.org/2016/05/05/cargo-pillars.html … - pretty different from https://docs.npmjs.com/how-npm-works/npm3-nondet …
-
@rustlang determinism itself isn't magic, but little modules often are shared (react, promise libs) and dups won't do -
npm3 reduces dups, but not reliably, which just makes the remaining problems even more baffling.
-
"just rm -rm node_modules && npm install" "worked for me" "ok closing" "doesn't work for me!" "can't repro sorry"
-
Ah, I see. Relies on SemVer to reduce dups then. Exposing types from a dep would still be an issue for interop...
- End of conversation
New conversation -
-
-
Surely small modules create their own issues, like a nightmarish dependency tree…
-
dependency trees are a problem ;) representing a graph as a tree works until it doesn't. Then you have nightmares.
-
That’s fair. Personally I feel like the small modules cargo culting is at least partially at fault.
-
It means that often boundaries between modules are poorly chosen.
-
definitely part of it. Any time people claim to have a silver bullet, be very very skeptical.
End of conversation
New conversation -
-
-
@nolanlawson@tomdale what about npm-lockdown, does it help? Otherwise how do we solve the problem? -
something like that, yes.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.