5 ms·
From the example of kickstarter, it seems completely undiscoverable -- things just keep happening and popping up and down, with no obvious indication of how, or
by CJefferson 9y ago
From the example of kickstarter, it seems completely undiscoverable -- things just keep happening and popping up and down, with no obvious indication of how, or why, those things were selected.
It's a demo which I'm sure appeals to emacs users, who are the target, but I couldn't imagine using it as a non-emacs user. I previously tried learning emacs to use OrgMode, and gave up after a couple of days when I failed to master even basic text editing skills.
- taeric 9y agoThe key bindings are typically very mnenomic. For example "s" stages, "c" brings up the commit window, "b" the branches window, etc. There are a few that go against this. "x", for example. But it really becomes almost conversational. Edit: corrected spelling of mnenomic. :) Not convinced it is correct word, oddly...
- funspectre 9y agoThe correct spelling should be mnemonic.
- deleted 9y ago[deleted]
- taeric 9y agoYeah, originally I put pneumonic. Which, is definitely wrong. I just keep thinking there is another word that is even more applicable than mnemonic. Guessing I'm just confusing myself.
- TeMPOraL 9y agoIt's actually very discoverable. The video lacked the sidebar showing the keypresses, though. Generally, each time you press a key that is part of a sequence, you get a pop-up explaining what further keys are available. So for instance, I opened magit (M-x magit-status) on a project and pressed ? (for help): https://i.imgur.com/c5cmmpB.png https://i.imgur.com/c5cmmpB.png The popup lists the keys I can use on magit-status page, and if you know git it's pretty obvious where to go in most cases. Also, at any time you can press ? and then one of the key listed in the popup to get a detailed description and/or an appropriate manpage.
- SadWebDeveloper 9y agoThis is my original point, tbh i didn't know about magit before this post, when i first opened the link and find out about it somehow i expected a GUI rather than a text-based app, m sure vim/emacs fans are excited about it but to me, this type of UIs (text-based) feel old and clunky. it's like we were still using norton/midnight commander for handling our files.
- lionel- 9y agoThe point of this kind of UI is that they become an extension of yourself. Saying these UI are old and clunky is exactly like saying a keyboard is old and clunky.
- SadWebDeveloper 9y agoSometimes 2-clicks can be faster than 2x 3-key combo just to make a feature work and also keyboards are old and clunky, ask any k-12 kid today and they will type faster on touch keyboard than a mechanical cherry-mx powered one. People still using text-based only IDEs for productivity are just prolonging the inevitable.
- taeric 9y agoOnly when training is lacking. And I don't mean this in a derogatory message, either. People that are trained with a keyboard are pretty much guaranteed to be faster than folks that have only learned to work with a mouse. Discover, though, will be much much faster with an exploratory interface. To that end, the mouse will lead to faster discovery in most cases.
- tarsius 9y agoMagit is definitely different enough from both your conventional GUI and command-line interface to make it hard to immediately see its benefits, which is why I did not only post some commented screenshots [1] (which may fail to impress), but also a text [2] which explains in what ways Magit differs from GUIs and command-line interfaces and what sort of benefits it draws from that. [1] https://emacsair.me/2017/09/01/magit-walk-through/#start https://emacsair.me/2017/09/01/magit-walk-through/#start [2] https://emacsair.me/2017/09/01/the-magical-git-interface/#start https://emacsair.me/2017/09/01/the-magical-git-interface/#st... A reason why it might actually be an advantage that the interface is "text based" is that the thing the tool interacts with is also text [3]. The primary difference to git is that the "output" is "actionable", the primary difference to GUIs is that every feature of git can be exposed quite naturally. [3] And a major advantage of that is that the barrier between writing the code and thinking of it in terms of change sets starts to break down.