4 ms·
Docker, it works on my machine. --- But to add a serious note, why is every dependency on the environment so complicated that we just wrap it in some containe
by sebazzz 7y ago
Docker, it works on my machine.
---
But to add a serious note, why is every dependency on the environment so complicated that we just wrap it in some container to just get rid of it?
- throwaway894345 7y ago> But to add a serious note, why is every dependency on the environment so complicated that we just wrap it in some container to just get rid of it? Bad build/dependency-management tooling and non-perfect abstractions over system APIs probably account for most of the issue. Containers are conceptually useful; it's nice to have ephemeral, isolated environments. But if it literally eats all of the CPU it can get its hands on, then it's not useful.
- lowmagnet 7y agoMy default is to use environment-based configuration (12f) while running in a scratch-or-at-largest-alpine-base image. This precludes a lot of things like shell-scripted startup, but then again, why are we running go if not to generate one binary as the entry point?
- ben0x539 7y agoBecause we've chronically underinvested in universally useful dependency management tooling, so the state of the art is a jungle of partial solutions that don't compose.