I prefer to recommend that developers try both vim and emacs at some point - that leaves the decision of whether to learn either (or both) entirely up to them. Personally, I know both, although I gravitate towards vim in the command-line. A lot of devs are scared off by the respective exit commands alone, so it takes some encouragement for them to try those editors in earnest, I believe.
That said, I do recommend that Linux ITs and sysadmins learn at least one power-user text editor. The time taken to learn vim or emacs quickly pays for itself when maintaining a server. (nano is a terrible option for that purpose.) Even if one has managed to set up their IDE or fancy window-system-based text editor to be able to edit remote server files, one should still know a good command-line editor; you can't always connect your favorite machine to the server when a fix is needed!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I prefer to recommend that developers try both
vimandemacsat some point - that leaves the decision of whether to learn either (or both) entirely up to them. Personally, I know both, although I gravitate towardsvimin the command-line. A lot of devs are scared off by the respective exit commands alone, so it takes some encouragement for them to try those editors in earnest, I believe.That said, I do recommend that Linux ITs and sysadmins learn at least one power-user text editor. The time taken to learn
vimoremacsquickly pays for itself when maintaining a server. (nanois a terrible option for that purpose.) Even if one has managed to set up their IDE or fancy window-system-based text editor to be able to edit remote server files, one should still know a good command-line editor; you can't always connect your favorite machine to the server when a fix is needed!