[vervas]

The perspective of the OP seems to stem from not having had to deal with the problems docker is trying to address. Most importantly it ignores the problems that arise on any dev team that is made up by more than one person.

One can do all the things that docker does without docker, but the knowledge needed to bring the basic features that docker does is far greater than learning how to use docker. In fact, if you know how to build something remotely close to docker, you'd be crazy not to use docker instead. At the very least, docker brings along industry standard conventions, and builds a common ground for everyone to work on without having to be onboarded on your home brewed packaging, distribution, storage, runtime and networking solution, regardless how simple it is.

On a side note, it seems like many trending topics on HN are heavily bashing new technologies (see k8s, rust, clouds, etc...) that are already widely adopted. Most communicate a resignation from learning something too complex. Docker is not complex, k8s is not complex, rust is not complex; the problems they are addressing are. Most teams developing things that run on the web will have to deal with these problems hopefully before they don't make it. The rest are wizards like the stackoverflow team.

[elric]

I don't think it's about "bashing new technologies" so much as it is about offering another perspective. Perhaps one that's less sexy, or perhaps one that's simpler and might work just as well in some cases. "XYZ SUCKS" posts are few and far between.