Re:Why I teach vim
by emidln on Sunday November 15, 2020 @04:06AM
(#25099527)
I work at a trading company on builds and developer productivity. vi is known by all 600+ people that touch code or admin systems as a baseline. I think we mention the basics in our dev school. If you need to edit somewhere outside your personal host, your choices are basically ed/vi. IntelliJ dominates Java development at well over 90%. CLion is what we teach for C++, but it's roughly 50% CLion, 30% vim, 10% Emacs, and 10% other (vscode mostly, but I've seen basically everything). I'm not sure of our Python breakdown, but I suspect IPython Notebooks/Jupyter dominates everything. For random edits, I see about 50% vi, 40% vscode/sublime, 10% emacs.
[ Parent
| on HN ]
On Windows, use Bitvise. SSH into your Linux box. Use the file browser GUI to navigate to your file. Edit it in Sublime, or your favorite editor.
Vi is ok for viewing files on a terminal, and for small edits, but it’s rather mediocre for any significant amount of development work.
> Vi is ok for viewing files on a terminal, and for small edits, but it’s rather mediocre for any significant amount of development work.
May I ask what prove this?
One of the statements I see a lot is that mouseless, keyboard only HCI is faster. But as far as I know, to the extent that any real studies have been done at all, this assertion is false.
I don't have the references at hand but I think people like Alan Kay and designers at Apple would think it crazy to even suggest that a keyboard only HCI is more efficient.
Could You please add a single example for faster solutions to modify several (text/source) files' contents at once with mouse and/or touchpad mainly (or any other already existing HCI interface)?