3 ms·
Aren’t you making the point of the author? Most places don’t have a way to run in development because they haven’t sat down and gotten the application to a run
by whb07 6y ago
Aren’t you making the point of the author?
Most places don’t have a way to run in development because they haven’t sat down and gotten the application to a running state. Every year it gets ignored, things get harder and more tedious but never impossible
- imoverclocked 6y agoI see both sides of this argument. Often legacy systems are tied to their deployment methodology/dogma and the world moves on from that model. Without a lot of resources poured into maintaining that methodology and upgrading it, the expected environment can age out of current practices far enough that running it locally does take a lot of effort. I think docker is an obvious enabler of this because people can just spin up an image from 6 years ago in a container and keep running against old libraries/dependencies. Even worse is depending on that container makes it difficult to upgrade dependencies to modern versions of software because the container is so old. Maybe a corollary to the article is, "without constant maintenance, software becomes un-runnable."