3 ms·

Its more like using the right tool for what you actually want to do. 0. Use cat and output to a file to really quickly make a new file from your clipboard or f

Its more like using the right tool for what you actually want to do. 0. Use cat and output to a file to really quickly make a new file from your clipboard or from the web 1. Nano is great for editing config / text files quickly and the learning curve is really low due to a more modern design. 2. vim can be reliably found everywhere on nearly any unix machine but the learning curve is much higher initial learning curve vim has more customization than vi and has basically replaced vi on modern installations of unix 3. emacs has out of the box has a learning curve less than vi but can't be found everywhere and you probably have to install it but it also has a large amount of extendability. the initial learning curve is a bit low but then it gets higher and higher. It also has multiple versions and a GUI and a package manager.

bityard 6y ago
> due to a more modern design nano is a clone of pico, the text editor for the pine email client, so "modern" is definitely a matter of some interpretation here. :)
- gbear605 6y ago
  It’s more similar to modern text editors, but yes it’s definitely more of a precursor
fouric 6y ago
> Nano is great for editing config / text files quickly emacsclient makes it just as easy to edit a text file extremely quickly with Emacs as to open a new vim or nano in place. > emacs [...] initial learning curve is a bit low but then it gets higher and higher Emacs's difficulty is, for simple editing cases that you could use nano for, only a little bit more difficult than nano, and certainly easier than vim - no modal editing, and you can learn the essential shortcuts (save, undo, open, close) in very little time. I don't agree that the learning curve increases - more complex things require that you learn more about Emacs, sure, but my experience has been that it's about as easy to go from beginner to intermediate Vim knowledge as it is in Emacs, if not slightly easier due to the latter's better design and documentation. > emacs [...] can't be found everywhere TRAMP has been around for two decades now, making this largely irrelevant - https://news.ycombinator.com/item?id=26982916 https://news.ycombinator.com/item?id=26982916
ch_123 6y ago
As someone who has invested time into vim, I can edit text files with it much quicker than I could with nano. I also suspect someone with sufficient nano experience may be as capable of coding in nano as I am in vim. "Use the right tool for the job" is all well and good (I mean, who wants to use the _wrong_ tool for a job?) but can lead to false dichotomies around tools which are designed to solve the same fundamental problems/use cases. I would posit that the model you suggest only is applicable to people with limited experience with vim, nano (and/or emacs). I would generally recommend that someone picks one and runs with it.

bityard 6y ago

> due to a more modern design nano is a clone of pico, the text editor for the pine email client, so "modern" is definitely a matter of some interpretation here. :)

gbear605 6y ago
It’s more similar to modern text editors, but yes it’s definitely more of a precursor

fouric 6y ago

> Nano is great for editing config / text files quickly emacsclient makes it just as easy to edit a text file extremely quickly with Emacs as to open a new vim or nano in place. > emacs [...] initial learning curve is a bit low but then it gets higher and higher Emacs's difficulty is, for simple editing cases that you could use nano for, only a little bit more difficult than nano, and certainly easier than vim - no modal editing, and you can learn the essential shortcuts (save, undo, open, close) in very little time. I don't agree that the learning curve increases - more complex things require that you learn more about Emacs, sure, but my experience has been that it's about as easy to go from beginner to intermediate Vim knowledge as it is in Emacs, if not slightly easier due to the latter's better design and documentation. > emacs [...] can't be found everywhere TRAMP has been around for two decades now, making this largely irrelevant - https://news.ycombinator.com/item?id=26982916 https://news.ycombinator.com/item?id=26982916

ch_123 6y ago

As someone who has invested time into vim, I can edit text files with it much quicker than I could with nano. I also suspect someone with sufficient nano experience may be as capable of coding in nano as I am in vim. "Use the right tool for the job" is all well and good (I mean, who wants to use the _wrong_ tool for a job?) but can lead to false dichotomies around tools which are designed to solve the same fundamental problems/use cases. I would posit that the model you suggest only is applicable to people with limited experience with vim, nano (and/or emacs). I would generally recommend that someone picks one and runs with it.