Iv been using vi because it’s built in. But real life experience is nano better? Easier? I basically cat into the file to make sure it’s what I want, then vi into it, tap I make my changes, :wq out and I’m done. So overall it’s fine, but it can feel a bit clunky navigating the file, is nano just a facelift or is there a lot of qol?
I would just install, but I don’t like messing with packages without researching first
--
[0] if you base that on chances of it being preinstalled, features, default colour scheme or the phase of the moon can only be determined by one person, you yourself.
When I started with Linux, I had to search how to use Vim/Vi as well, and when I used a system with Nano as default editor, I had to research again. I don't see a functionality issue here, just preference.
You can freely install nano and stick to it without a negative impact on the system's workings.
vi is everything but beginner friendly, but you can use it for everything, from software development to writing books (LaTeX). Admittedly, most would prefer vim over busybox vi on systems with sufficient resources.
--
Disclaimer: I am using vim for basically anything that touches configuration- or source files of various programming languages.
I think vi/vim is more beneficial to learn as it is pre-installed on almost every Linux system. But as has been stated nano is just fine if you prefer it.
My personal take is that I very much enjoy editing in 'vi'. Editing in 'vi' is an acquired taste that might be compared with drinking wine or whisky; once acquired, you will always favour it over drinking an alcopop like Smirnoff Ice. If you imagine Neo from the Matrix, he would definitely be using 'vi' rather than 'nano' or 'emacs' .
Some may laugh at this (and likely have merit in doing so), but in developing my various OpenWrt projects on GitHub I actually just edit the files on my router using 'vim' and upload to GitHub using git on the router. I find it cool how all that can be done over ssh.
Just my 2¢:
I use mc/mcedit/mcview whenever I can (and in OpenWrt I mostly can).
Both vi and nano are "acquired taste"... I failed to acquire even if/when forced to use them.
Personally, I sped far too little time inside any one editor to become fully proficient, so for me editors that give some visual feed back about what commands they support are really helpful, so for my OpenWer needs I either use nano or mc's editor and vi only if out of other options
Isn't vi just a BusyBox extension on OpenWrt, like lots of commands? Makes sense to just use that instead of spending extra space on a separate text editor, by default.
If you can learn the basics of vi (not vim, or vim-enhanced, or any of the more modern variants) then you'll be doing just fine in the vast majority of Linux and POSIX compliant UNIX distributions, especially in emergency/rescue/single user mode.
Learning any other editor's syntax after that is just gravy. Or custard, depending on preference
I normally use vi, for heavy-duty jobs (i.e. software development, browsing multi-megabyte files, etc) I switch to GNU Emacs. I'm too old to try nano, I'd rather use Wordstar.