# Dependency policy - should we avoid dependencies or embrace them?

**URL:** https://discourse.julialang.org/t/dependency-policy-should-we-avoid-dependencies-or-embrace-them/8793
**Category:** General Usage
**Tags:** dependencies
**Created:** [February 3, 2018, 11:44am UTC](https://discourse.julialang.org/t/dependency-policy-should-we-avoid-dependencies-or-embrace-them/8793 "2018-02-03T11:44:12Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)
#### Post date: [February 4, 2018, 4:14pm UTC](https://discourse.julialang.org/t/dependency-policy-should-we-avoid-dependencies-or-embrace-them/8793/15 "2018-02-04T16:14:45Z")

</div>

This is just about having a good developer target. If a package is sufficiently large that people are trying to depend on a small portion of it, it should be organized to have a small developer target. No one should depend on a plotting package, just RecipesBase.jl. No one should depend on DifferentialEquations.jl, just the parts you use (DiffEqBase.jl, or things like OrdinaryDiffEq.jl). No one should depend on all of JuliaOpt, just JuMP.jl and whatever solvers you use. Etc.

---

_[View the full topic](https://discourse.julialang.org/t/dependency-policy-should-we-avoid-dependencies-or-embrace-them/8793)._