Yeah, what I don't understand is that he seems to completely ignore the fact that a docker containers is still running linux, just isolated in a new filesystem (and more technologies I don't know a lot about like namespaces and stuff)
So the author thinks it's better for users to do (sometimes tedious) steps to get an application or a set of applications running, just for them to "know how to use linux", while ignoring the fact that Docker/containerization's primarily use case is for the developer side, and the developer needs to know linux to write a working Dockerfile.
Kinda. Yeah. Ignorance really isn't a virtue, and at some point bending over backwards to support people that don't want to learn things is counterproductive.