|
|
|
|
|
|
by lproven
14 days ago
|
|
|
OK, fair enough. I first learned Vi on SCO Xenix in 1988 and I instantly hated it, and 38 years later, I still do. About 2-3Y into my career, IBM CUA came along and transformed DOS software: everything got a new CUA UI. Word 5, proprietary UI; Word 5.5, CUA. WordPerfect 4, proprietary UI; WP 5, CUA. Since then, if an editor isn't CUA, life is too short: I won't even consider it. There's a standard PC UI. All Linux GUIs follow it more or less, except for the ones that intentionally chose to Do Something Else, to Be Different for Difference's Sake. (GNOME, Elementary, a few others.) It's time the shell/console world caught up. Leave the old one as an option for the old timers. Everyone else gets CUA by default. But that's just me. |
|
|
I've since learnt the tool. Its ubiquity (particularly over pretty much all of the other ones I'd listed, at least on the machines I had ready access to) cemented that.
I did like EVE when I'd used it, but have had little access to VAXen since. And was proficient for a time on Emacs (until a subsequent gig's director insisted that if it didn't come installed software wouldn't be added to our Unix server). My WP-fu fell with the end of DOS, though I did hang on for quite some time, up to the late 1990s / early aughts.
CUA has its benefits, but it is only one of multiple competing keyboard standards. Everything is convention.
Oddly: I'm vi/vim in the editor, but readline on the shell. No, I don't set vimkeys bindings in Bash. But I do drop to bash as my shell editor.
Also: for those stumbling across this thread later, "Mastering the Vim Language" is an excellent video I'd come across in my third decade of using the editor, and learned much from. It's now 11 years old itself:
<https://www.youtube.com/watch?v=wlR5gYd6um0>
Vim may have a long learning curve, but it also has a steep payoff function.