I've used Vim, NeoVim, Micro, mg(1), JOE, and even MS Edit (both the original DOS version and the recent Rust clone). No matter how complex and tailored I wrote my config, though, the features I actually used were included in GNU nano and/or my command shell without any of the bugs, bloat, learning curve, or slop.

Using it as my default just makes sense.

I use helix for all my developer work and nano for "I need to edit this config file buried somewhere in /usr/...". I never remember to do Sudo -E

Best local simple terminal text editor is micro.

oh no, not again.

Sometimes I catch myself opening nano inside emacs' term. I literally forget I'm using emacs and just do it on instinct. I once also opened emacs inside emacs' term and I just stared at the screen in disbelief.

It's there and it's easy. Most people don't use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.

Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything... Even when I'm using SSH, because vscode supports SSH

People don’t have to look up “how to exit nano”

I'm in the "been working with Linux since the 90s" gang so I call vim vi and nano pico and when I started there was a coolness factor to be considered. I was incredibly uncool so I used whatever I wanted, including pico - I mean you used pine for email back in the day and the interface was nearly identical, so whatever.

But I did want to be at least a tiny bit cooler, so I learned vi in a fairly rudimentary fashion. I can edit, jump, delete, search, replace, copy and paste - oh, and I can exit. I've spent so much time using vi, that my brain doesn't even have to think about exiting, not even whether I want to write or not. It just happens like second nature. It's actually gotten to where nano seems unduly burdensome to me.

But really, I prefer an IDE for programming. CLI editors will always be for configuration files and shell scripts to me.

I like Nano; it lets me do what I need to do quickly, simply and efficiently.

Many were increasingly of the opinion that they’d all made a big mistake in making text editors in the first place. And some said that even making operating systems had been a bad move, and that no one should ever have built computers at all.

It is preinstalled and does what it needs to do. What else can I ask for?

Same reason people use notepad on windows. It's already installed on almost every distro

I see Hitchhikers Guide to the Galaxy parody, I updoot

I've wanted to move elsewhere for a long time, thing is I don't use nano for programming, I use it for config files. For programming I use an IDE, and every time I've tried leaving my IDE for emacs with a language server I find I just can't be bothered to set it up and learn it and make the move. Maybe because while I have some gripes with my current setup...they're very minor

I'm part of the "learned Linux when I got my first raspberry pi" gang, and all Ras pi tutorials tell you to use nano. So yes.

Nano is to EMacs/Vim as Notepad is to Notepad++ or VSCode (Nano has features Notepad doesn't, but you get the point).

I don't do a ton of code editing directly on the CLI. I do things like change parameters in config files or open a file to read it quickly. If I'm doing more heavy editing, I'll use a GUI editor (with an SFTP extension if I'm working on a headless server). So programs like Vim and EMacs have never been useful for me.

To each their own (and I have all the respect for anyone who knows how to exit Vim without looking it up) but I'm guessing the majority of people have a similar experience.

Not long ago, I needed to quickly add a 4-line thing to my Ruby on Rails app on my Raspberry Pi. I was like, shit, I really can't be arsed to mount the RPi over Samba to edit this stuff on VSCode on my Windows laptop to add like 4 lines. I don't have vim, I can't be arsed to check which vimlike I have at hand, I can't be arsed to see if my Emacs setup has been customised for this RPi. So fuck it, Nano it is!

The Venn diagram of nano users and Debian/Ubuntu users is a circle

I have been around since production servers were predominantly HP-UX, Solaris, and AIX. I settled on Vi because it was the one common editor that was preinstalled on every *NIX OS, including Linux and you could jump right into edit mode while reading a file without having to exit the preview first.

Nano is fine, but one you've gone through the pain of committing Vi to muscle memory, there's no point to switch.

Big fan of micro. Like nano, it's non-modal, but unlike nano, it doesn't need to print its shortcuts on the bottom because everyone already knows most of the shortcuts from almost every GUI editor. And it has inbuilt LSP support (TBH it's a bit much at times, the UI is a bit too intrusive to (by default) complain every time you violate some style guideline).

Though that's moot if you don't have admin privileges on the box you're working on.

I think Vim is great if you use it everyday and know it inside out. For those of us who don't, Nano is just easier, not least because it tells you in the UI how to exit it xD

I only ever use to quickly edit some config file and for that i really don't need anything more complex.