4 ms·
I think arguments about productivity miss the point and Carmack is actually right that typing speed isn't the bottleneck. I think the reason programmers love t
by Barrin92 6y ago
I think arguments about productivity miss the point and Carmack is actually right that typing speed isn't the bottleneck.
I think the reason programmers love to tinker with their vim or emacs configs is because it's simply satisfying. Just like a blacksmith has their very own set of valued tools, there's something extremely rewarding about configuring your setup just the way you want it. You work your entire life with it, so you might just as well make it your own, I think that's what people get out of it, just a subjective sense of making things fit right.
It's like my barber who has some cool vintage scissors he got from someone. Could he cut my hair with some high grade scissors he bought on the internet? Sure, but he likes his ones better. At the end of the day programming is more like a craft than a science and it shows when it comes to topics like this.
- srtjstjsj 6y agoPeople generally don't tinker with vim/emacs for editing. They tinker for the IDE features that Carmack says are valuable.
- Reelin 6y agoFor me at least it's more than "simply satisfying". It gets the UI out of the way. It's removing a number of mild distractions and nuisances that are otherwise there all the time. It's not about typing speed at all (for me). It's about having a clean and orderly working environment where the number of frustrations have been minimized.
- blub 6y agoOn the other hand it's typically quite easy to customize the UI of IDEs and hide menus and such to the point that it's possible to tune out whatever is left. Therefore I'm tempted to look at this problem not from a technical but rather from a social perspective: I consider this preoccupation with editors as a kind of fixation and way of exercising power in a straightforward way as a part of an increasingly complex and unfriendly environment. We can't customize the stupid Scrum processes guiding our lives, can't customize the management which often is rather clueless about what we're doing, can't avoid that most software projects are ultimately pointless even if they claim they're changing the world and empowering users. But we can certainly customize our editors. And then there's the social pressure from the typical hacker circles which would happily dictate what programming languages, tools and paradigms are good and which are bad. Of course this scaffolding all comes crashing down when one looks at the results and there's no discernible difference between the quality or success of projects where various editors or processes or languages are used. So the focus moves to personal benefits, personal preferences and programming as craft and so on. But it's all just a game programmers play, isn't it?
- Reelin 6y ago> customize the UI of IDEs and hide menus and such That's not even half of it. TUI programs are designed to be keyboard driven from the start, not as an afterthought. All the IDEs I'm aware of are hopelessly outclassed here. There's also things like registers, column editing, and the buffer abstraction which make common tasks less cumbersome. The list continues. It's not that one tool can be used for a task that the other can't; rather it's just better at it from my perspective (given my particular workflow and toolchain). For me, there's a significant ergonomic difference which makes for a more pleasant process overall. Is keeping a clean and orderly workspace "just a game"? What about using the best (from your perspective) tool for the job? I imagine different people will care about these things to different degrees. As you point out, perhaps for some there's primarily another motive (exercise control, irritate a coworker, maintain an appearance, ...). That's not mutually exclusive though and it's hardly unique to programming.
- chongli 6y agobecause it's simply satisfying I think there’s more to it than that. Yes, it can be very satisfying to tinker with one’s tools rather than getting work done. But that doesn’t explain someone like me who took the time to learn vi (not vim) rather than using a basic text editor like nano or Notepad or TextEdit. So why would I take the time to learn vi? I don’t tinker with it (beyond adjusting a few basic settings like autoindent, line numbers, incremental search, etc). It certainly took me a long time to get very proficient with vi. It’s also the case that any editing task I can do with vi can be done in any other text editor (they’re all “text equivalent”). The answer is that vi, more than any other editing method, removes friction from the editing process. Having used it for a long time, I’ve built up muscle memory that allows me to rapidly jump around files and make precise edits. It also lets me easily automate repetitive editing tasks with its ex commands, macros, and of course the humble ‘.’ command. In the case of more elaborate tasks such as paragraph formatting, table formatting, or inserting line numbers into the text, vi lets me easily pipe motions, ranges, or buffers through shell commands. So why doesn’t everyone use vi? Well that’s specific to personal taste. Some people don’t get as frustrated by friction in the editing process as I do. Maybe John Carmack doesn’t mind reaching over to grab the mouse in order to move the editing cursor somewhere else, or to select text for copy and paste. I don’t know what his editing environment and workflow look like. Perhaps he uses some other editor like vi but with the default configuration. I guess there’s one more piece to clear up and that’s the question of whether or not I qualify as a “power editor user”. I think I do. I don’t tinker with my editor to the incredible extent that some others do, for sure. I used to tinker and found it a deep rabbit hole of distraction which inevitably led me to a slow and complicated environment (highly customized vim) that really didn’t do anything fundamentally faster/better than I could already do in plain vi. Having said that, I think my experience with vi (including having purchased and read O’Reilly’s book on the topic [1]) has helped me to master its commands far more thoroughly than a typical vim user. So I think that qualifies me as a power editor user. Others may disagree. [1] https://www.oreilly.com/library/view/learning-the-vi/1565924266/ https://www.oreilly.com/library/view/learning-the-vi/1565924...
- mucholove 6y agoIt’s also much easier to tinker with your editor (at least at the very beginning of your coding career) You get immediate feedback on every change. It feels like you’re doing something. For much of my self-taught coding ability, I’ve been tinkering with configuration files that don’t seem to move the needle. The time I spent on my editor was the distraction.
- pmoriarty 6y ago"I think the reason programmers love to tinker with their vim or emacs configs is because it's simply satisfying." I spent a ton (no, really a metric ton) of time tweaking my vim and emacs configs, and have thousands of lines of code in each, but I haven't touched either in years, and I'm pretty happy with that. Yes, tweaking editor configs is fun, but I have other interests too, and those other interests have taken priority for a long time now. Incidentally, I consider all that time tweaking my configs very well spent -- not because it was fun, but because my editors are enormously useful to me now, and I wouldn't dream of ever going back to more primitive editor.
- eloff 6y agoI actually pick type. I'm pretty fast and I can do it without looking at the keyboard. Although I can't switch keyboards easily and I buy multiple of the same keyboards at a time because of this. I've found it doesn't hold me back compared to touch typers. Data entry speed is just not the bottleneck. On my best day I might write between 500-1000 lines of code, which is just not that much typing spread over 8-12 hours. Average days are adding/modifying maybe 200 lines. Typing or editing speed here just really isn't the issue.
- ATsch 6y agoI personally don't think it's particularly rewarding, I hate touching my vim config. But I still use it because, while typing is definitely not a bottleneck, it is still something I'd otherwise need to actively think about. Vim lets me compose the concepts I use when thinking about the language, like parameters, blocks, tags, lines with editing operations directly. Deleting a block (dab) becomes just that, from muscle memory with no mental translation to concepts like backspace or selections required. I'm sure with enough practice you can get really fast at that too, but I don't think the amount of mental effort and context switching can be as low.
- lenkite 6y agoWhen I used Keyboard and Mouse combo, I suffered from crippling wrist pain. I stopped getting this when I shifted to VIM - use VIM editing in every IDE and application now.