this post was submitted on 10 Oct 2023
42 points (76.9% liked)
Programming
17026 readers
176 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.