Modern “vi” is typically a symlink to vim, and as long as compatibility is disabled it’s very useful; especially when working over ssh or quick and dirty config editing that doesn’t warrant a full blown ide to be started up.
Nano is for people that are too lazy to learn vi if they much time (ergo not needing it)or have too less time to learn it (even tho, they would get so much time back in return, if they would learn vi)
This applies only to people that regularly work with GUIless headless machines
Okay I kinda get it if you regularly write scripts or configs on headless machines, though even then I’d think using just vscode remote development plugin would be my tool of choice.
Usually I use nano if I just need to do a quick change to a file, or even on my personal device if it requires sudo (such as apt sources or fstab) and I do it just once so don’t bother thinking how to use sed for it
Modern “vi” is typically a symlink to vim, and as long as compatibility is disabled it’s very useful; especially when working over ssh or quick and dirty config editing that doesn’t warrant a full blown ide to be started up.
Nano is for that purpose
It is a pain for larger files. It small and light but doesn’t have the same featureset.
Nano is for people that are too lazy to learn vi if they much time (ergo not needing it)or have too less time to learn it (even tho, they would get so much time back in return, if they would learn vi)
This applies only to people that regularly work with GUIless headless machines
Okay I kinda get it if you regularly write scripts or configs on headless machines, though even then I’d think using just vscode remote development plugin would be my tool of choice.
Usually I use nano if I just need to do a quick change to a file, or even on my personal device if it requires sudo (such as apt sources or fstab) and I do it just once so don’t bother thinking how to use sed for it