|
|
|
|
|
by jyaker
3831 days ago
|
|
That actually makes your point even more of a Straw-Man. It's non-trivial for most teams to setup personally managed dependencies for their dependencies (e.g., cvs, package management, etc.). Maybe it's just my experience, but outside of the enterprise realm, I generally don't see that sort of thing. |
|
> Maybe it's just my experience, but outside of the enterprise realm, I generally don't see that sort of thing.
Most programmers are more interested in jumping into every new sexy library that just happened to appear than to make their working environment reproducible, robust, and controllable. That's why they don't think of how to package their code for installation and deployment, don't think where and how to keep their dependencies (not thinking about dependencies causes explosion of dependency fractal, which is a collateral damage), don't think how to work off-line, and so on.