21 ms·
Sure, but if someone is trying to get into *nix SA, or even cloudy/devopsy/CI stuff, you really do need to learn vi/m.
by indigodaddy 6y ago
Sure, but if someone is trying to get into *nix SA, or even cloudy/devopsy/CI stuff, you really do need to learn vi/m.
- ilaksh 6y agoWhy? It's just as easy to install micro as it is vim. sudo apt install micro or curl https://getmic.ro https://getmic.ro | bash Or just download the binary from github.
- indigodaddy 6y ago*nix system administration at many companies means that there are 1000s of RHEL or CentOS or older Solaris servers that you may very often need to edit a file if there is no config management (which is often the case). What all these servers will have to do that will be vi (or vim if you’re lucky). In most cases you can’t just go install some random other text editor that you happen to like better or be more proficient in. That means you have to be at least somewhat functional in vi to be able to perform basic tasks.
- ilaksh 6y agoIf you literally have to log into an ssh session on 1000s of machines running discontinued operating systems to manually edit files and can never install new tools for editing or anything else in those machines, then you deserve to go out of business.
- indigodaddy 6y agoBut aren’t you talking about sshing into a machine and manually editing with Micro? If we’re going to talk apples, let’s stick with talking apples.
- theonemind 6y agoIn my experience, that's not a real option in large, professional system admin settings. You wouldn't dare do that on a production machine without your change management process, and your team of admins won't care about installing micro on the thousands of machines you have to manage. You'd have to do a pull request to some kind of config management repo, and no one will agree your pet editor merits a deploy, and your boss will think you're wasting everyone's time. I'm not covering half of it. Trust me, it is just generally not an option for system administration in the large.
- ilaksh 6y agoYou're right, of course it's impossible for anyone to approve installing a modern editor. How ignorant of me to suggest that. Everyone must use the editor and paradigm from the late 1970s. That's the only way professional system administrators and organizations can operate. No one has time to approve a pull request, no matter how outdated the editor is. We all learned it. Everyone else has to learn it also. Until the end of time. Amen.
- Brian_K_White 6y ago"How ignorant of you." is exactly correct.
- indigodaddy 6y agoI mean, I’d be surprised if the percentage of SAs that are proficient in vi is less than 90% (even that percentage is probably low), so I really don’t think it’s a problem that needs to be solved. vi/m works superbly as the main text editor on *nix servers. Sounds like you just hated it from the get go and refuse to learn it. And that’s also fine.
- ilaksh 6y agoI learned it and use it all the time. It's just an outdated editor and religion. And there is no logical reason not to replace it with something modern and superior. And it's a shame that people are suggesting that young people waste their time with it. It's just amazing that says admins are literally suggessting they can't install a program.
- indigodaddy 6y agoGiven its prevalence in the SA landscape (which I don’t think even you can deny), to state that learning Vi would be a waste of time for any young person interested in the industry, would be, well, completely inaccurate. But we obviously completely disagree. We can just probably leave it at that.