3 ms·
> Firstly the model of sshing into your server and trying to run commands on it directly is more or less obsolete. Why do you get to declare what is acceptable
by cranekam 5y ago
> Firstly the model of sshing into your server and trying to run commands on it directly is more or less obsolete.
Why do you get to declare what is acceptable (using UNIX tools) or what's now obsolete (SSHing into a host)? It's rather presumptuous to believe you can speak for everyone. Perhaps you only ever deploy code using k8s and never need to use a command line but that doesn't mean we all do. There are many reasons one would use these tools and approaches (fun, small scale, investigating problems, anything).
- ccalloway 5y agoYou might think 'fun, small scale, investigating problems' are good justifications for your working practices, but your boss's boss's boss does not. They would prefer you to have less fun. Or perhaps to have fun on your own time after being laid off.
- herbst 5y agoMy boss (me) doesn't mind me dabbling around in my servers via SSH. Not everyone of us works for evil cooperate.
- ccalloway 5y agoThat's fine but you are proving my point. I didn't say that no one uses shell, just that there aren't good practical reasons for doing so. Of course lots of people do it because they enjoy it or are used to it, and for them cost and related considerations don't matter. The same way that lots of people ride horses.
- cranekam 5y agohead in hands For what it's worth, my bosses all the way up to CEO of a 50k person company were all pretty pleased with the working practices I used (medieval things like strace(1), perf(1) and sort(1)) to save thousands of servers' worth of CPU. I'm not advocating for editing code live over SSH but there are still plenty of legitimate reasons to SSH into a server and use UNIX tools. Since you're clearly trolling I'll leave it here.