Actually I would say collaboration is a huge win. Right now we do shared screens when we have to do some CLI operation.
I know and have worked at companies with very complicated setups for CLI-based workflows where you need 2 people to agree for each command. This could potentially solve all of that.
That being said, with the move to containers there's a lot less CLI surgery to do.
But hasn't collaboration and stuff been a thing for as long as time-sharing machines have?
Besides, Service as a Software Substitute is NEVER a good idea, I don't want to go to someone else's server to do something I could on my own, especially when I have to pay taxes for it...
By the way, can you define "CLI surgery" for me? I used Unix for a while but haven't played with containers beside chroot jails, and I suspect all that is just your company overcomplicating simple things.
My point is mostly that shell isn't cross-platform, and this is one way you could address that. But it's not a generalized solution, absolutely.
(and yeah, something like Python is better than trying to keep multiple of the same scripts in different languages, for sure. You can do it if you wanted though, if they're small and you're willing to commit to it, I'm not sure I've ever seen it really pulled off.)
basically every operating system has a posix shell by default except windows, but it has been ported there multiple times, samba existed for decades and WSL is on the rise. It may sound a little more irritating but they deserve it for still running windows :p /hj (besides you can just host an ssh server)