It seems pretty clear to me what this means. Unlike, say, a GNU/Linux command line environment, Kubernetes is not a lived-in environment. Certain kinds of environments (at least in the free software world) naturally accrue small conveniences just because they are used for basic things like navigating the filesystem, communicating with others, writing the text that one spends 40+% of their day on, etc.
Kubernetes just isn’t such an environment. For most people nowadays (although this was once the case), neither is a mainframe.
Without the natural pressures of
habitation, a computing environments can retain certain kinds of sharp edges much longer.
That said, we may not agree with the author’s idea of the coziness of Unix. But what he’s getting at there, the claim itself, is perfectly clear.
Wat.
Literally copied and pasted that from the article.
I know. I’m responding to the absurdity of it.
It seems pretty clear to me what this means. Unlike, say, a GNU/Linux command line environment, Kubernetes is not a lived-in environment. Certain kinds of environments (at least in the free software world) naturally accrue small conveniences just because they are used for basic things like navigating the filesystem, communicating with others, writing the text that one spends 40+% of their day on, etc.
Kubernetes just isn’t such an environment. For most people nowadays (although this was once the case), neither is a mainframe.
Without the natural pressures of habitation, a computing environments can retain certain kinds of sharp edges much longer.
That said, we may not agree with the author’s idea of the coziness of Unix. But what he’s getting at there, the claim itself, is perfectly clear.