I was talking with a sysadmin once who intentionally removed nano and emacs from any system he was granted access to. His explanation was “if they can’t use vim I don’t want them on my machines”
As a VIM user, I don’t want you using VIM on my system unless you know how to use it. I don’t want you borking fstab or the passwd file or some other important config because you don’t know how to quit without saving.
Brilliant! I don’t entirely disagree with that. I had vim forced on me at my old job, including actual vi on some of the more ancient systems. I got so used to it that I don’t really know how to use nano and definitely not emacs.
I never understood what the big deal was. Write. Quit. If you can’t remember that ‘w’ means write and ‘q’ means quit, I don’t know how else to help. Add in some decent options in your vimrc and it is pretty comfortable. I am in no way some guru who knows every shortcut and fancy command out there, but I like using it and it is the first thing I install on a new system.
I am not one to judge what text editor, OS, phone, car, or computer you like. You do you. If I was a sysadmin that had to deal with people who really shouldn’t be on those systems and that was an easy way to discourage people from screwing with it, then hell yeah.
Knowing VIM does not make one a better sys-admin. You can be an idiot, and still know how to drive Vi/Vim. There is FAR FAR FAR more to managing an OS and than that. If you think requiring VIM is enough to keep unknowledgeable people away from servers, you are probably the one who shouldn’t be managing servers.
I was talking with a sysadmin once who intentionally removed nano and emacs from any system he was granted access to. His explanation was “if they can’t use vim I don’t want them on my machines”
There’s a sysadmin at my place who does exactly that. He’s kind of an idiot too.
As a VIM user, I don’t want you using VIM on my system unless you know how to use it. I don’t want you borking fstab or the passwd file or some other important config because you don’t know how to quit without saving.
Lol love this.
Shocked
If a sysadmin expected me to use vim for every minor config tweak, I wouldn’t want to be on their machines either.
Sounds like it works then.
Once you get the hang of it it’s just so much quicker for small and big tasks.
Check out vim adventures:
https://vim-adventures.com/
Or just install vimtutor and try around. The basics are pretty simple, and the more advanced stuff infinitely helpful.
Thanks, no. At that point i use sed, grep or a GUI editor.
Why? Nano doesn’t need training, and even for config the engineers shouldnt be able to impact production without review. Sysadmin needs to retire
I don’t find nano any easier for minor tweaks than vim
A vim user finding nano too difficult? Impressive.
Brilliant! I don’t entirely disagree with that. I had vim forced on me at my old job, including actual vi on some of the more ancient systems. I got so used to it that I don’t really know how to use nano and definitely not emacs.
I never understood what the big deal was. Write. Quit. If you can’t remember that ‘w’ means write and ‘q’ means quit, I don’t know how else to help. Add in some decent options in your vimrc and it is pretty comfortable. I am in no way some guru who knows every shortcut and fancy command out there, but I like using it and it is the first thing I install on a new system.
I am not one to judge what text editor, OS, phone, car, or computer you like. You do you. If I was a sysadmin that had to deal with people who really shouldn’t be on those systems and that was an easy way to discourage people from screwing with it, then hell yeah.
Knowing VIM does not make one a better sys-admin. You can be an idiot, and still know how to drive Vi/Vim. There is FAR FAR FAR more to managing an OS and than that. If you think requiring VIM is enough to keep unknowledgeable people away from servers, you are probably the one who shouldn’t be managing servers.