Beyond Editor Preference: The Case for Text-Based Interfaces
Quite often, someone online asks whether they should make the switch from VS Code to Neovim. There are countless forum posts, video essays, and debates in which people advocate for their editor of choice. One side says Neovim made them work faster and they would never go back; the other says VS Code already does everything they need, without spending weeks memorizing keybindings. The discourse surrounding the subject got me curious enough to make the switch myself. Having used both, I find that the debate usually focuses on surface-level details. The more fundamental question is not which editor looks better, is easier to configure, or has better plugin support; it is whether an interface like Neovim's is worth the effort at all. Text-based interfaces are worth learning for programmers because their keyboard-first design pushes users onto a faster way of working, and their text-only nature means they work anywhere there is a terminal, including remote machines with no graphical environment.
The first advantage of a text-based interface is that it keeps users on the keyboard, which research shows is the faster way to issue commands. In a study of Microsoft Word, Lane et al. found that, with both hands on the keyboard, issuing a command using a shortcut took an average of 1.36 seconds, compared to 2.17 seconds for the icon toolbar and 3.13 seconds for the menus (141). In other words, clicking through menus took over twice as long as pressing a shortcut. In a text-based interface, commands are issued via the keyboard, so users work at the faster speed by default. While it is true that typical GUI-based applications also support keyboard shortcuts, users often do not use them. As Lane et al. put it, "Highly experienced users of Microsoft Word make little use of the efficient method of keyboard shortcuts, relying, instead, on the less efficient icon toolbar and menu methods" (139). Nor did the habit fade with time: "greater experience with the software was not indicative of the use of more efficient methods" (139). Put simply, users stick with the path of least resistance even when a faster method exists. Text-based interfaces build the habit of using shortcuts from the start, since there are no mouse-driven menus to fall back on.
The more a shortcut is used, the less thought it takes. In a 1985 paper on interface design, Hutchins et al. quote a user of vi, the predecessor of Vim and Neovim: "I am an expert user of vi, and when I wish to delete a word, all I do is think 'delete that word,' my fingers automatically type 'dw,' and the word disappears from the screen. How could anything be more direct?" (327). The authors credit this ease to practice rather than to vi's design, noting that "when tasks are practiced sufficiently often, they become automated, requiring little or no conscious attention" (327). Since every command in a text-based interface goes through the keyboard, users get that practice simply by using it.
A second advantage of text-based interfaces is that, because they only require text, they work anywhere there is a terminal. That includes machines where a graphical environment is either missing or impractical, such as a remote server accessed over SSH, a headless Raspberry Pi, or an old laptop too slow to run a desktop comfortably. In a survey of 300 system administrators about firewall interfaces, Voronkov et al. collected comments on the strengths of command-line tools, and one respondent explained, "I can do the same task via an SSH connection or even a KVM [keyboard-video-mouse console] if the whole network is down" (263). Another noted that the command line "uses zero system resources" (262), which matters on hardware too weak to run a desktop. Some GUI-based applications do offer remote capabilities, most notably VS Code's Remote-SSH feature, but they require more setup. One of the respondents Voronkov et al. surveyed raised this exact issue with GUIs: "A software client can be needed, which may not always be accessible" (266). A text-based interface, by contrast, only needs the terminal that is already there.
The main drawback of text-based interfaces is that they are harder to learn. In Voronkov et al.'s survey, it was the most common complaint about command-line tools: "The main problem, which was referenced 19 times, is a long learning curve" (263). Lane et al. frame this as a trade-off, noting that "menus and icon toolbars are easier to learn, whereas keyboard shortcuts are more efficient" (133). That trade-off is worth making, since a shortcut only has to be learned once but saves time with every use. The same authors point out that "it would not be unusual for a user to issue hundreds of commands a day, and the accumulation of small time savings could be considerable" (141). To quote Bram Moolenaar, the creator of Vim, "Learning to drive a car takes effort. Is that a reason to keep driving your bicycle? No, you realize you need to invest time to learn a skill."
Should someone make the switch from VS Code to Neovim? The specifics of which editor someone uses matter less than the interface behind it. For programmers, the speed text-based interfaces build and the machines they reach make them worth the effort. While the steep learning curve can seem intimidating, it does not have to be climbed all at once; picking up a handful of commands in one tool is enough to start.
Works Cited
Hutchins, Edwin L., et al. "Direct Manipulation Interfaces." Human–Computer Interaction, vol. 1, no. 4, Dec. 1985, pp. 311–38, https://doi.org/10.1207/s15327051hci0104_2.
Lane, David M., et al. "Hidden Costs of Graphical User Interfaces: Failure to Make the Transition from Menus and Icon Toolbars to Keyboard Shortcuts." International Journal of Human-Computer Interaction, vol. 18, no. 2, May 2005, pp. 133–44, https://doi.org/10.1207/s15327590ijhc1802_1.
Moolenaar, Bram. "Seven Habits of Effective Text Editing." Moolenaar.net, Nov. 2000, http://www.moolenaar.net/habits.html.
Voronkov, Artem, et al. "System Administrators Prefer Command Line Interfaces, Don't They? An Exploratory Study of Firewall Interfaces." Proceedings of the Fifteenth Symposium on Usable Privacy and Security, USENIX Association, 2019, pp. 259–71, https://www.usenix.org/conference/soups2019/presentation/voronkov.