As a new sys-admin, what text editor should I use?

If you are not going to spend a lot of time in the terminal you could just use nano because it is quite easy to get used to.

But if you are planning to become a real Linux SysAdmin, then it is definitely worth learning vim even though it is a much steeper learning curve than nano.

Hi janbridges,

For a junior SysAdmin I would recommend nano as it’s the easiest.

I’ve seen a lot of senior System Administrators use nano. I’m talking about people with more than 15 years of experience in the field. When I asked them why don’t they use VIM (which I was trying to learn at the time), I got a pretty straightforward answer, VIM is too smart for it’s own good, nano is the way to go.

Now, VIM has more useful packages and function. For example highlighting variables, loops etc. depending on the extension of the file which is really cool. Having said that, I feel for a junior System Administrator nano is better as a starting point.

PS. If you actually configure nano, it can also have highlight.

Kind regards, Kalin D.

Hi janbridges,

For a junior SysAdmin I would recommend nano as it’s the easiest.

I’ve seen a lot of senior System Administrators use nano. I’m talking about people with more than 15 years of experience in the field. When I asked them why don’t they use VIM (which I was trying to learn at the time), I got a pretty straightforward answer, VIM is too smart for it’s own good, nano is the way to go.

Now, VIM has more useful packages and function. For example highlighting variables, loops etc. depending on the extension of the file which is really cool. Having said that, I feel for a junior System Administrator nano is better as a starting point.

PS. If you actually configure nano, it can also have highlight.

Kind regards, Kalin D.

Hi janbridges,

For a junior SysAdmin I would recommend nano as it’s the easiest.

I’ve seen a lot of senior System Administrators use nano. I’m talking about people with more than 15 years of experience in the field. When I asked them why don’t they use VIM (which I was trying to learn at the time), I got a pretty straightforward answer, VIM is too smart for it’s own good, nano is the way to go.

Now, VIM has more useful packages and function. For example highlighting variables, loops etc. depending on the extension of the file which is really cool. Having said that, I feel for a junior System Administrator nano is better as a starting point.

PS. If you actually configure nano, it can also have highlight.

Kind regards, Kalin D.

Hi janbridges,

For a junior SysAdmin I would recommend nano as it’s the easiest.

I’ve seen a lot of senior System Administrators use nano. I’m talking about people with more than 15 years of experience in the field. When I asked them why don’t they use VIM (which I was trying to learn at the time), I got a pretty straightforward answer, VIM is too smart for it’s own good, nano is the way to go.

Now, VIM has more useful packages and function. For example highlighting variables, loops etc. depending on the extension of the file which is really cool. Having said that, I feel for a junior System Administrator nano is better as a starting point.

PS. If you actually configure nano, it can also have highlight.

Kind regards, Kalin D.

If you primarily are connecting to machines to fix configs and the like, then definitely get to know vim.

That said, as you scale out things, you hopefully won’t be doing as much ssh’ing to machines to edit files and instead will be editing some configuration management system like chef, ansible, etc. In this case it is good to spend time with a programmers editor, which could be vim as well! Emacs is another great choice as it has tons of helpful features for working with many different languages, taking notes, and interacting with other systems (ie TRAMP).

I’ll admit I jumped on the Emacs train long ago and happily recommend it to folks, but vim is great too. In vim, I think you typically end up using other tools like tmux, fzf, etc. increase productivity where as in Emacs, you end up using different plugins. Choose what makes sense to you!

If you primarily are connecting to machines to fix configs and the like, then definitely get to know vim.

That said, as you scale out things, you hopefully won’t be doing as much ssh’ing to machines to edit files and instead will be editing some configuration management system like chef, ansible, etc. In this case it is good to spend time with a programmers editor, which could be vim as well! Emacs is another great choice as it has tons of helpful features for working with many different languages, taking notes, and interacting with other systems (ie TRAMP).

I’ll admit I jumped on the Emacs train long ago and happily recommend it to folks, but vim is great too. In vim, I think you typically end up using other tools like tmux, fzf, etc. increase productivity where as in Emacs, you end up using different plugins. Choose what makes sense to you!

If you primarily are connecting to machines to fix configs and the like, then definitely get to know vim.

That said, as you scale out things, you hopefully won’t be doing as much ssh’ing to machines to edit files and instead will be editing some configuration management system like chef, ansible, etc. In this case it is good to spend time with a programmers editor, which could be vim as well! Emacs is another great choice as it has tons of helpful features for working with many different languages, taking notes, and interacting with other systems (ie TRAMP).

I’ll admit I jumped on the Emacs train long ago and happily recommend it to folks, but vim is great too. In vim, I think you typically end up using other tools like tmux, fzf, etc. increase productivity where as in Emacs, you end up using different plugins. Choose what makes sense to you!