Are you afraid of dependencies?

Are you afraid of dependencies?

02cd14759ba3327f68f737131947781f?s=128

Glen Mailer

July 20, 2017
Tweet

Transcript

  1. 3.
  2. 7.

    Rando on HN https://news.ycombinator.com/item?id=10571452 “This is why developers should try

    to avoid introducing dependencies. Not at all costs, of course, but typical project in JavaScript, Go, Ruby, or Python has way, way too many dependencies, while little of them have any significant benefit.”
  3. 8.

    Prominent Clojure community member “The ideal number of dependencies for

    a library release (not counting Clojure itself) is zero. Obviously, use common sense. If your library relies on critical functionality in another library, then make the dependency. But if you can get by without the dependency (even if that means copying some of those "utility" functions into your own code and making them private) then you will make life easier for consumers of your library.”
  4. 13.

    Manifest of things to depend on A version for each

    thing Download from some central location Will pull in dependencies-of-dependencies aka transitive dependencies Arrange artifacts suitably for runtime module loading
  5. 17.

    Global v Local Test v Dev v Real Package/Import symmetry

    Vendoring Snapshots Ranges Lockfiles Do Applications need versions? X Replaces Y (props to PHP's composer)
  6. 21.

    Pick a version of D for you 1. Your app

    might work 2. copy-paste from C 3. upgrade B to work with D@2 4. don’t use C, write your own thing
  7. 22.

    Tell you it can’t resolve 1. Tell it you know

    best 2. copy-paste from C 3. upgrade B to work with D@2 4. don’t use C, write your own thing :pedantic? :abort
  8. 25.
  9. 26.

    Allow both to co-exist 1. Your app might work 2.

    copy-paste from C 3. upgrade B to work with D@2 4. don’t use C, write your own thing
  10. 32.
  11. 34.

    Less time spent keeping up Lowered cost of creating dependencies

    Smaller dependencies Less reasons
 to change Less changes
  12. 35.