Why shouldn't it be as easy to write system administration programs in Go as it is in a typical shell?
1. Shell scripting offers infinite functionality. You can shell script with any program in any language. All it needs to do is take input and produce output. And if the functionality doesn't exist, you can create it on the fly, without having to follow any of the traditional rules of programming.2. Shell scripting is a combination of a grammar, operators, a few simple functions, and an extremely loose coupling with generic i/o and logic. I don't know Go well, but it probably doesn't support a similar flexibility. (most languages are very proscriptive about how you can use the language, so you usually can't make things as easy as they are in a different, more tailored language/interface/paradigm. this is why we have DSLs)
3. Programmers don't really understand the concept of productivity [outside of programming itself]. A programmer would solve a problem by taking 6 weeks to design a perfect program to do the thing. A Sysadmin would take 5 minutes with a shitty language and a shitty tool and get way more done in less time. And re-writing everything into a Go library would always be slower than shell scripting, because it requires re-implementing what a shell script would just use as-is.
Scripting is duct-taping the wheel rather than reinventing it. If you want to save yourself a whole lot of time and trouble, just use the duct tape.
(also: don't go templates exist? why isn't that used for scripting)
[1]: https://leancrew.com/all-this/2011/12/more-shell-less-egg/
Both from the technical and the marketing point of view having a car that can do better than any human ever could, even in the most optimal of conditions would be a great thing.
My hunch is that this is related to the question of why we are experiencing this particular moment in time and not another one in the past or in the future, is related. If you believe in the many words interpretation of quantum mechanics, one can also say why I’m experiencing this particular branch.
For example, when somebody touches someones hand in your view, your mirror neurons activate just like you yourself have been touched. Then your nerve endings in your hand send a signal to cancel the effect, but sometimes you still get a tingling from the neural confusion depending on the strength of the signal (e.g. watching someone getting kicked in the balls or russian daredevils walking on top of highrises). But, if there is no nerve endings there, there is nothing to cancel the signal, so you do experience another persons feeling of being touched as your own. Therefore, the only thing that separates our consciousness is literally our skin and our nerve endings on it.
https://en.wikipedia.org/wiki/Eiffel_Tower_replicas_and_deri...
But for more mundane stuff, even phasing out media storage technology periodically causes a giant loss of knowledge and means even with the help of archiving groups.
I also stated that I'm ambivalent about the worth of such knowledge preservation, whether it is a form of stamp collecting or something more foundational. All I have to compare is the fact that we have an estimated %1 of Ancient Roman literature surviving and I'd prefer to have at least a bit more of it.
I do admit I didn't have a point to make really, or to assign worth to an ancient gauntlet. Rather it was a reflection on losing stuff while finding stuff and the permanence of marks we leave on this world.
Maybe it is a creeping anxiety about losing knowledge as we stride forward and forgetting the means of recreating the things we end up with. Kind of like the Dark age of technology in WH40K.
Even NASA was unable to establish contact with the IMAGE satellite after 18 years. I do see the false equivalence here, yet it is nonetheless thought provoking, alongside 100+ year old tea shops in Japan.
I'm not sure what is currently being done at developing git, but adapting/creating some porcelain commands accommodating a more centralized workflow even mainly on a semantic level could help with the UX friction.
Also, the obligatory joke "git gets easier once you get the basic idea that branches are homeomorphic endofunctors mapping submanifolds of a Hilbert space"
"The Dread" is a good north star for discovering what to improve next, since most Dreads are somewhat common/shared among peers, communities and colleagues. Being able to do something nobody likes to do is a good edge against the world.