I hope that whatever solutions we come up with to handle the too-many-dependencies problem don’t stifle people’s motivation to create and share new packages. It’s not a given that useful libraries are going to exist. Too much friction and people will just stop sharing code.
-
-
My sense is that is only a recent development, and it has only come up because people are starting to make noise about it. IMO anyway. We need to keep encouraging folks to think critically about bringing in dependencies.
-
It really depends, though. In the Pathfinder library I’ve tried to avoid use of mandatory dependencies—that’s why it’s split up into so many crates so that you don’t get e.g. SVG parsing unless you need it. But the examples use tons of dependencies, because they’re examples.
- 2 more replies
New conversation -
-
-
I'd very much like to be better automated detection API breaking changes and how that reflects to semver, reviewing and signing code with crev and "const fn only" deps to be a thing. In my mind, those three would make it a lot more manageable.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.