You must have great internet that has symmetric upload and download speeds. When I’m home (in San Francisco with $100+/month connection), the difference between pushing a 12mb image and a 100mb or 300mb image is 10 minutes.

At work I don’t care because our connection is symmetric but while upload speeds are routinely 1-5mbit, if you are lucky (on dsl it’s worse), it matters.

If you're shipping a binary image back upstream, you're doing it wrong.

Artifact builds absolutely positively should never happen on developer workstations. Perform local builds as a test, but always push your build instructions and source to a centralized builder.

If you even remotely respect the folks who depend on binaries of your code as a developer, you will avoid shipping those binaries yourself. Send build instructions to a 3rd party and allow them to distribute the binary and keep yourself honest.

Solution : no need for super fast home internet when dealing with docker images .. get yourself a server (VPS) on ovh.com for $7/mo 4gb ram and do your docker image builds and push there to avoid having slow uploads from home ... total game changer ... the gives you the liberty to work from even a slow internet connection since there is slim to no bandwidth needed to issue commands on remote server via ssh connection

I don’t know if it’s changed, but it hasn’t been that easy to cleaning up old images in Docker, so small images can save a lot of disk space on a QA environment where containers are continuously created and destroyed, for example.

Also, it’s probably a lot easier to cut off a few megabytes off an image than fixing Atoms ram usage.

I suspect that most of those of us that make a hobby of minification (whether it be container images, JavaScript, images or anything else) use Vim or other non-wasteful text editors.