6 ms·
Ok let me be very honest here, let's look at both editors learning curves - vi/vim You need to learn to open a file, edit it, move around and exit and the edi
by raverbashing 8y ago
Ok let me be very honest here, let's look at both editors learning curves
- vi/vim
You need to learn to open a file, edit it, move around and exit and the edit/view mode. Everybody learns how to do it. At first it sucks but you can learn this in 5 min.
Nothing too hard, and yes, do use the direction keys, it's not the 70s anymore.
From there you can learn other things
- Emacs
You try reading anything about it, there's something about Meta key (and apparently nobody can say what the actual meta key is without some wrangling from them because who knows if you're not coding on a Sun Sparc from the 90s so they don't want to compromise).
Then something about a "prefix command" C-x (what is C? Control? Which other program uses C as an abbreviation for that?) Buffers. What's a buffer?
I tried opening the help of both programs, VIM shows exactly what I mentioned there. Move around, close this window, etc
Emacs? I'll copy-paste here (key bindings help)
> C-x Prefix Command
> \200 .. ÿ encoded-kbd-self-insert-ccl
> C-x 8 iso-transl-ctl-x-8-map
Why the F is this relevant or useful?
Then I try to quit and it's a bit of a wrangle until it gets Ctrl-C Ctrl-X right (or the other way)
Everything seems like it's actively fighting the user, and making it more difficult or convoluted than it should.
Usability problems are never the fault of the user.
- zealsham 8y agoHave you tried exiting vim? :D
- raverbashing 8y agoYes, I press F1 (help) it shows me this: > Get out of Vim: Use ":qa!<Enter>" (careful, all changes are lost!) The joke is not relevant anymore
- JD557 8y agoI know this was intended as a joke, but exiting vim is now much easier than exiting emacs (IMO), assuming that the user has some experience with UNIX and uses `Ctrl+C` to exit most programs. If I start vim and press `Ctrl+C` I get an helpful message saying "Type :qa and press <Enter> to abandon all changes and exit Vim". If I do the same on emacs, first the help screen disappears (which was the one telling me to use `C-x C-c` to exit emacs and then I just get stuck with an unhelpful message about creating new files.
- scbrg 8y agoYou could try opening the File menu and selecting Quit :)
- atilaneves 8y agovim is a text-mode program. Emacs is not. Exiting is easy for anyone, just click the x in the window and poof! It's gone.
- thomasahle 8y agoTry exiting `ed`. Much more fun.
- cup-of-tea 8y ago> You need to learn to open a file, edit it, move around and exit and the edit/view mode. Everybody learns how to do it. At first it sucks but you can learn this in 5 min. > Nothing too hard, and yes, do use the direction keys, it's not the 70s anymore. All of that applies to emacs too. What's the difference? > Usability problems are never the fault of the user. That's contrary to the old saying: a bad workman always blames his tools.
- jholman 8y ago> That's contrary to the old saying: a bad workman always blames his tools That is not what that means. If GP had said "I cannot write good code in Emacs", that'd be a poor craftsman blaming their tools. But saying "this tool is not as effective as this other tool" is a thing that good craftsmen do. (I'm not addressing the original claim, just meta-meta-critiquing your meta-critique).
- raverbashing 8y ago> All of that applies to emacs too. What's the difference? It's in the post > That's contrary to the old saying: a bad workman always blames his tools. It doesn't go contrary. Some tools are bad, some don't. That's why I choose the tool that doesn't get in the way and don't blame me for not joining their cult: vim
- close04 8y agoUsability is always and without a doubt the responsibility of the designer. The old saying might be valid for tools that are meant for complex tasks. Expert level tools where doing the job a certain way is more important than doing it intuitively. In reality that saying is mostly used as an excuse for a tool that could be more effective but isn't. If something as basic as a text editor is so unintuitive it is not the user's fault. There's always the option of providing better examples or documentation, or a more intuitive "control scheme" which allows users to toggle between "old" and "new". The fact that some tools choose to do it "the hard way" is almost entirely rooted in tradition and reluctance to do it another way. Not because it's better.
- krylon 8y ago> use the direction keys, it's not the 70s anymore. In my experience, the fact that I can navigate a file without taking my hands off the home row far outweighs any disadvantages hjkl might have. With emacs, the big point is that you can do so many things in it that you never have to leave it; that also means once you have the keyboard shortcuts memorized, you can use them everywhere - besides editing text, emacs can serve as a mail client, a web browser, an IRC client, a music player, telnet/ssh client / terminal emulator (kind of), you can even play Nethack in emacs. You can't expect to become fluent in emacs within a couple of minutes, but if you are willing to stick around, the time spent learning emacs pays off big time.
- TeMPOraL 8y ago> that also means once you have the keyboard shortcuts memorized, you can use them everywhere That's half of the benefit. The other half is, in Emacs things compose and interoperate. That fancy autocomplete plugin you just installed? It will work for suggesting e-mail addresses just as well as for suggesting function calls in code. Multiple cursors? Regex search-and-replace? Keyboard macros? They work everywhere, whether you're writing code, exploring the filesystem, composing e-mails or tweeting/tooting on Mastodon. That's the reason many people, myself included, try to move as much of their workflow as possible into Emacs. The right thinking is this: Emacs is an application platform for everything that uses text (or can be made to use text), and has much better defaults and interoperability capabilities than your regular operating system.
- bunderbunder 8y agoAs great as that is, though, they're all advantages that won't become relevant until you've really learned emacs, and won't become really advantageous unless you're comfortable enough with emacs that you're willing to commit to it. In other words, its not stuff that's going to drive adoption. The ggp has a point about emacs having a higher barrier to entry for complete beginners.
- krylon 8y agoBut having to spend a lot of time getting familiar with some tool, language or framework is not unusual in IT/Programming. Think of C++, or the .Net framework. When programming in C#, I spend at least 1/3 of my time browsing the API documentation or StackOverflow, TechNet, etc. With emacs, as with C++ or .Net, the idea is that the effort to get familiar with the environment pays off big time after a certain point. If somebody asks me (that happens almost never, though), my reply is to tell them about the long term-benefits of using emacs and to give both emacs and vi a try and decide what they like better. And that emacs vs. vi is not necessarily an either-or-decision. I use emacs as my main editor, but I often find myself editing config files using vi. I prefer emacs, but vi/vim is an excellent editor, too. More generally speaking, if somebody tries to frame something like the choice of editor as an either-or-question, consider if a-as-well-as-b is a valid answer, too.
- TeMPOraL 8y ago> Nothing too hard, and yes, do use the direction keys, it's not the 70s anymore. Yet another thing 70s got better than today's software. The defaults you're used to are a historical accident, and are also crap - that is, an impediment to productivity. > I tried opening the help of both programs (...) > Emacs? I'll copy-paste here (key bindings help) How on Earth did you get there? The very first thing in the Help menu (also conveniently bound under C-h t, and also conveniently listed in help-for-help view that shows if you press C-h C-h) is the Emacs Tutorial. The thing that's designed to teach you the basics quickly. Just read and follow the instructions, and it will all make sense. As for whatever you just pasted here (looks a bit like output of C-x ?), it's probably part of the self-documenting aspect of Emacs, which you're yet to discover. That is, you can get help and documentation on absolutely everything - including runtime values of key bindings, variables and functions (both C and elisp) used by Emacs. > Everything seems like it's actively fighting the user, and making it more difficult or convoluted than it should. It's not. It's just: - following a (somewhat) consistent set of UX principles that are older than IBM CUA (which gave you CTRL+C / CTRL+V, etc.). Older does not mean worse. - a tool for serious users, who are not afraid of spending 5-15 minutes reading the tutorial. To be clear, I'm not arguing here for Emacs over Vim. I'm arguing here against the stupid - and stupidly common - approach that proper UX means a newcomer must be able to use the software productively after 30 seconds of exposure to it. It's a stupid approach, because the only way to do this is to dumb down the program to the point it does so little that it can be mastered in 30 seconds. Emacs, like Vim, and Blender, are tools for people who want to be productive. A prerequisite here is the willingness to learn something.
- raverbashing 8y ago> The defaults you're used to are a historical accident, and are also crap Agreed, that's why I use modern IDEs as well when vim gets in the way > How on Earth did you get there? f1 + ? then "describe bindings" which looks like the most relevant option (I had opened a file with emacs first, I see the welcome page has more helpful guidance, but opening a file is usually what people do first) > following a (somewhat) consistent set of UX principles that are older than IBM CUA Sure, it's the same with vim, old standards > a tool for serious users Thanks for reinforcing my point that Emacs is more worried about gatekeeping people than being friendly
- JdeBP 8y agoYou pressed the wrong foot-pedal for help, there. * http://jdebp.info./Humour/exiting-emacs.html http://jdebp.info./Humour/exiting-emacs.html
- OskarS 8y agoYour comparison is a little unfair. If you just want to use it as a text editor, Emacs is easier to use than Vim. You can move around with the arrow keys, typing letters inserts them into the document, there are the standard menus, toolbars and scrollbars you would expect. In other words, if you're looking for a "Notepad replacement", Emacs works just fine as that, and you don't have to learn anything about the meta key or whatever. I agree that Emacs overall is more complex overall (which is not necessarily a bad thing), but from a "first impressions" perspective, Emacs wins.
- erikbye 8y agoTo first-time Emacs users: Do M-x (alt-x) and type help-with-tutorial, hit your enter key (RET in Emacs jargon).
- michaelmrose 8y agoWhen you first open emacs the first buffer says ";; This buffer is for text that is not saved, and for Lisp evaluation. ;; To create a file, visit it with C-x C-f and enter text in its buffer" It comes with a Menubar as found on most applications and rightmost is one labeled help, the first entry goes to the tutorial "Emacs tutorial. See end for copying conditions. Emacs commands generally involve the CONTROL key (sometimes labeled CTRL or CTL) or the META key (sometimes labeled EDIT or ALT). Rather than write that in full each time, we'll use the following abbreviations: C-<chr> means hold the CONTROL key while typing the character <chr> Thus, C-f would be: hold the CONTROL key and type f. M-<chr> means hold the META or EDIT or ALT key down while typing <chr>. If there is no META, EDIT or ALT key, instead press and release the ESC key and then type <chr>. We write <ESC> for the ESC key. Important note: to end the Emacs session, type C-x C-c. (Two characters.) To quit a partially entered command, type C-g. To stop the tutorial, type C-x k, then <Return> at the prompt. The characters ">>" at the left margin indicate directions for you to try using a command. For instance: >> Now type C-v (View next screen) to scroll down in the tutorial. (go ahead, do it by holding down the CONTROL key while typing v). From now on, please do this whenever you reach the end of the screen." It goes on at length covering all basic aspects of using emacs. Under the help menu there is also an extensive manual. If this isn't discoverable enough a logical response would be to type Emacs tutorial into your favourite search engine and read at least one of the results. You say "Usability problems are never the fault of the user." and your not wrong per se but tools have intended audience and reasonable expectations. Scalpels and coffee pots are made for different users and its challenging to make a scalpel that would enable a surgeon to remove an appendix without having to crack a book. Microsoft office which is aimed at a much broader and less skilled user base makes it very easy to enter a little text but its very normal for users to receive training, google for answers, and RTFM. Regardless of what anyone hopes neither vim or emacs are much used by random joe to read their email they are tools made by technical people for technical people. Given the audience I don't think its unreasonable to suppose that people who bypass both tutorials, and manual in favour of describe bindings and leave without a pit stop at the search engine might be the cause of their own discontent. Let me make a wild guess here. You got frustrated. Took a minute to consult google to figure it out and moved on but you left that part out because it didn't support your position.