3 ms·
Indeed the docker revolution was the Dockerfile and container images: the latter a convenient way to store and share container binaries and the former a conveni
by afiori 4y ago
Indeed the docker revolution was the Dockerfile and container images: the latter a convenient way to store and share container binaries and the former a convenient way to define recipes for the latter.
This is also what they are trying to do with wasm and what (in part) GitHub did with git: creating a developer ecosystem.
- adamgordonbell 4y agoI never thought of the parallels to git but that is interesting. So git is to github as (chroot/cgroups/unionfs) is to docker et all? What is the VC company that is going to spring up around WASM?
- afiori 4y agoDocker itself is trying to expand into wasm applications: https://news.ycombinator.com/item?id=33320530 https://news.ycombinator.com/item?id=33320530
- treffer 4y ago> So git is to github as (chroot/cgroups/unionfs) is to docker et all? You could do docker-alike runtime things with lxc and e.g. squashfs filesystems. That is IMHO a good signal to say it's not the tech. I see it more as developer workflows. Github looked at git and LKML working model and put that into a centralized UI. The revolution was individual contribution (not teams) and personal repositories. (Does anyone remember the other scm hosting tools before? I remember running some open source sorceforge alike thing) Docker took all the pieces before you could run a container and made those easy to achieve (building, sharing, pulling, ...). That's developer workflows.
- suprjami 4y agoVery insightful comment. The developer ecosystem is always the primary path to success. The same thing with Raspberry Pi. There are a million $notmuch single board computers with fruit names, but the Raspberry Pi has dominated much more powerful systems for 10 years now because of its top-tier software.