5 ms·

if you are preparing your own env, then I agree, but if you want whole team/company to share the same env then it's useful tool even with all complications it i

if you are preparing your own env, then I agree, but if you want whole team/company to share the same env then it's useful tool even with all complications it introduces. its even more useful when your dev env need to be updated fairly often.

poulsbohemian 4y ago
Yeah, I get that’s the idea… I’ve just never seen it work, and any context for me has turned into a “what is docker actually doing for me in this context?” When I worked with specialized hardware / OS dependent things, we needed to bring up full VMs with our config. When I worked in shops with lots of microservices, it was better to actually run against the current integration environment rather than try to bring them all up locally. For so many apps, package management is the important part in terms of consistency from one machine to the next. So - I get what other people tell me about docker, I’ve just never been able to make sense of it as useful in my dev environments and teams. In fact, the one team I saw that really committed to it hard, it was a cluster (and maybe that’s why I have a trauma response toward it).
- nikau 4y ago
  Its just a rehash what devs did in the 90s, ie. have a zip or tar file of an installation directory of dev tools and utilities. We used to do it back then with everything statically linked or libs put into a folder with a LD_PRELOAD variant for whichever unix os they were on. And it makes sense - if you have ever had to support a large team of developers you find out that a lot of them are totally siloed into their development niche and most have no idea around how to debug a bash script or troubleshoot issues when they encounter a simple deviation from the onboarding instructions. Then you have fun things like there being 2 conflicting versions of yq out in the wild and conflicting utilities if someone has installed GNU tools in preference of the mac versions and a docker image makes a lot of sense.

poulsbohemian 4y ago

Yeah, I get that’s the idea… I’ve just never seen it work, and any context for me has turned into a “what is docker actually doing for me in this context?” When I worked with specialized hardware / OS dependent things, we needed to bring up full VMs with our config. When I worked in shops with lots of microservices, it was better to actually run against the current integration environment rather than try to bring them all up locally. For so many apps, package management is the important part in terms of consistency from one machine to the next. So - I get what other people tell me about docker, I’ve just never been able to make sense of it as useful in my dev environments and teams. In fact, the one team I saw that really committed to it hard, it was a cluster (and maybe that’s why I have a trauma response toward it).

nikau 4y ago
Its just a rehash what devs did in the 90s, ie. have a zip or tar file of an installation directory of dev tools and utilities. We used to do it back then with everything statically linked or libs put into a folder with a LD_PRELOAD variant for whichever unix os they were on. And it makes sense - if you have ever had to support a large team of developers you find out that a lot of them are totally siloed into their development niche and most have no idea around how to debug a bash script or troubleshoot issues when they encounter a simple deviation from the onboarding instructions. Then you have fun things like there being 2 conflicting versions of yq out in the wild and conflicting utilities if someone has installed GNU tools in preference of the mac versions and a docker image makes a lot of sense.