8 ms·
I dunno, I never sat down to learn vim, just used it every day for a couple years. I’m not one of those wizards who is, like, answering stack overflow questions
by bee_rider 4y ago
I dunno, I never sat down to learn vim, just used it every day for a couple years. I’m not one of those wizards who is, like, answering stack overflow questions or writing wiki articles, but I get the job done. Is it necessary to learn Vim? Seems like a chore.
Is the text editor really a bottleneck for anyone? I find that no matter how slow I type, I need to spend more time thinking of what to type anyway, if I’m doing anything interesting.
- X6S1x6Okd1st 4y agoI similarly have mostly not learned vim, but every now (usually on fridays) I spend a bit of time seeing if there's an easier way to do something. My recent learning was :quickfix. I normally build in a terminal anyways so this was a pretty nice little speedup for iterating on static analysis results or a build problem.
- tambourine_man 4y agoMany years ago, decades actually, I used TextEdit + services shortcuts to filter text through grep, sed, awk. I found even syntax highlighting a distraction. Then I saw someone using Vim. I was instantly hocked. The sheer speed of everything happening in the screen, I needed to learn that. And so I did and it’s been an amazing ride. It’s a pain at the beginning, the amount of time I invested in my .vimrc will probably never payoff, mathematically speaking. But the joy and delight you get from using it everyday, the freedom and efficiency is just addictive. It’s not for everyone, I was raised on the Mac paradigm, where “modes are evil”, so it was a step learning curve. But few programs have brought me this much joy and excitement over the years.
- blindhippo 4y agoIt’s not a bottleneck for anyone. Some people just like playing with tools. They do it for loads of reasons, but end of the day it’s basically a hobby tangentially related to software development. I torment a friend of mine who talks all the time about VIM and their most recent config/workflow. But end of day, he’s happy and having fun while being productive.
- scooble 4y agoI feel that your last point is underappreciated. I enjoy my work more if I enjoy using my tools, and I enjoy using vim.
- antisceptic 4y agoI don't understand this attitude. It's clearly more conducive to solving problems to be able to move around our environment more quickly. It's extremely useful (compared to a beginner who only knows insert and write quit) to understand the different vim modalities as well as a few commands to jump around a file or to perform regex or to call an external command. When you're not proficient with the necessary tools, you're interrupting your flow with what you consider mundane. That you consider text editors mundane is more reason to move as much of that process into muscle memory as possible, not less! Why are we pretending like mastery of our tools is unimportant? I hear this sort of opinion most eagerly expressed by engineers who in fact are quite handy with vim! Is this some new kind of flex where we're all pretending to take a purely academic approach to programming instead of becoming proficient with the tools of our trade?
- blep-arsh 4y agoThis is true for tools in general but I've managed to master vim to the point I can be somewhat productive yet it never feels quite ergonomic. Moreover, I think vim-like UI is holding everyone back nowadays. Learning all the intricacies of vim feels like an exercise in brute-forcing a deliberately user-hostile design. For example, is it really still OK to have little to no visual feedback when entering commands with range/count prefixes, or to have to fall back to custom commands and configs in order to search for strings containing "/"? Or have commands with tiny edit distance between them do radically different things (e.g. "w! " and "w !")? Vim's modal editing implementation also can't handle non-Latin keyboard layouts so I find myself switching keyboard layouts all the time (e.g. normal mode->insert mode->layout switch->type some text->layout switch->normal mode).
- lycopodiopsida 4y ago> Vim's modal editing implementation also can't handle non-Latin keyboard layouts This issue is solved by langmap.
- blep-arsh 4y agoIt really isn't. I've spent a lot of time trying to tune langmap/keymap and looking into other options but the result is mostly unsatisfactory. Some of the issues: only translates the first letter of the command; doesn't support :commands; isn't expressive enough to remap punctuation. Vim needs to be keyboard layout-aware in order to support non-Latin keyboards. It also needs to know whether the current input state is expecting text or a command (e.g. typing ":s/" from the normal mode should always be parsed using the Latin layout but the currently active input language should be used following the "/").
- hodgesrm 4y agoI'm insatiably interested in most technology but learned vi and vim commands largely through typos.
- sanderjd 4y agoYeah I think vim style modal editing is really useful, but honestly I get about 70% of the value from doing it "wrong"; using a fast key repeat and holding down hjkl, using visual mode a lot, etc. It really doesn't need to be this mystical uber-hacker thing to be useful.
- bambataa 4y agoI do the same and agree, though I’m trying to push myself to be a little more sophisticated. The beauty of doing it that way is that it takes no thought. I want to select from here to just after that letter P. With hjkl and visual mode I’m already halfway there. Whenever I try something clever I always find myself thinking “is that the end of a block? Or maybe I should cut directly to P but oh there’s another one on the line above so it’s the second, need to amend” etc etc etc.
- sanderjd 4y agoYeah I guess the next like 25% of the value I get from vim comes from "df(" and "ct)" type commands. Also "dd" and "p" a lot to move lines around and "J" to consolidate them. So maybe I do use a pretty large amount of functionality pretty frequently :) I've been thinking maybe that other comment nailed it and most of us who downplay how useful it is to really learn vim have just already done that and forgotten that it was really useful.
- cess11 4y agoWhat vim can do that emacs often is a little too slow for and IDE:s can't is to have finished even quite complicated incisions and changes to your text before you've become conscious that you asked it to do the thing. This means it can help keep out intrusions about editor maneuvering from your mind at work. Some people see no value to this and fill their vim bundle with plugins that slow everything down a lot, but some of us really enjoy just surfing the high source and watching our thinking materialise on the screen seemingly effortlessly and immediately. I use IntelliJ all day every day too, but it's mainly for admin and control stuff and certain types of refactors it can handle better. It's to my code editing as gitk is to my version control. It's where I run the tests, all the plugins, can get docs prerendered, things like that. It's not where I can quickly navigate the code base, jumping immediately from file to file as fast as a fuzzy hint can get me, and then within the file as fast as Space+string can get me. You might have a keyboard layout with a forward slash easily available, mine doesn't so in normal mode space is /. Navigating in vim can be hjkl w b and so on, sure. But it can also be search. Just say the place and poof, you're there. It's wrong but very similar to where you want to go? n for next or try to name a new place. This doesn't work in IntelliJ and it's a little off in emacs. I mean you can certainly technically do it but it's slow. There's waiting and the application twitches when it tries to imitate the vim way. Pretty much all finding tasks can be powered by fzf and ripgrep, and unlike IDE:s vim just does the thing when you tell it to. There's is no wait and then a dialog, there is none of 'ok, understand but Ide competent, knows many things, need more info before can do the thing' that tools like IntelliJ and Visual Studio do. You also want jk to be Esc for sure. Esc is far away and CapsLock is for Control.
- vdm 4y agoyou had me at > 'ok, understand but Ide competent, knows many things, need more info before can do the thing'
- pama 4y agoI agree with all except that Emacs is a bit too slow or a little off for these tasks. Emacs is rather easy to extend and modify to make exactly fit your task if you want to. Out of the box search is decent and very easy to make better than fzf. Ripgrep is cool and when used within Emacs you can also edit the search results and save them back to all files at once if you want to.
- stevekemp 4y agoIn the past I was mostly the same, but then I realized that I was doing myself a disservice by not fully knowing my tools. Every month or two I'd read a manpage for something and really experiment with using all the facilities - most of them wouldn't stick, but every now and again some would. Just pick something like "less" or "bash", read the manpage, and try using something you've not done before. It's very helpful. For Vim I went through the tutorial a few times a long time ago, and that really helps. (For twenty years I used emacs for "everything", and vim solely for email, via mutt and later my own client.)
- _glass 4y agoYou are right and wrong. I paired with a lot of juniors, and especially in the beginning stage of your career it is important to write as fast as your thoughts are. And in the same way, to be able to jump directly to the place where you want to change something. I belong to the Emacs tribe, and macros were really so impressive while doing my Masters for a lot of people, mass-changing classes definition through "programming" without really thinking. Still, mastery in macros impressed people and saved projects through really fast iterations, it's faster than Excel or Python. It's that a lot of times, you have a thought and want to execute on it, seeing the result immediately. What I don't like about Emacs and Vim is the lack of great debugger support. I would love a world where unit testing, functional data structures and static typing obliterate debugging, but we're not there yet. What I encountered is, that actually real mastery of tools made or broke projects. The 80/20 rule is not what I observed in reality. It is really long tails all the way.
- the_gipsy 4y agoBottleneck, yes but who cares. Your code or work won't be any better. It just removes a lot of frustration, that's the thing for me. Working less on fiddling with text is focusing more on the conceptual level. Again, I'm not claiming the output is better, I'm just happier doing it.
- citrin_ru 4y ago> I find that no matter how slow I type, I need to spend more time thinking of what to type anyway It true that thinking takes more time than typing/editing even you type slow and don't use any hotkeys for editing, but I have a feeling that the less time/effort I spent on typing/editing the less my thinking is interrupted. With some practice one can use quite a few vim features relying on 'muscle memory' to spend less time/effort on editing and concentrate on what matters - thinking.
- 127 4y agoI tried it. It's good for editing system configs on a Linux system through SSH. That's about it. A lot of people are trying to fit a square peg into a round hole. People also want to appear hip and cool, "hackery". Boring and well known is like oil to the average programmers water.
- BossingAround 4y agoI love editing configs and fiddling around with a system over SSH with vim. Then, I have to do the main part of my job and put the changes into a YAML file for Ansible automation, which I do in VSCode :)
- nonima 4y ago>I need to spend more time thinking of what to type anyway Do you think everything through and then implement it? I do most of my thinking as I type.
- magpi3 4y ago> Is it necessary to learn Vim? Though I no longer program, I am still a huge VIM enthusiast, but no it is not necessary to use VIM. I just love it because it made me more efficient, but at times I think that writing code really really fast might actually be a bug and not a feature. For editing code it's amazing though. People looking over my shoulder used to think I was a wizard.