Notes on switching to Helix from vim

Notes on switching to Helix from vim

Julia Evans

I haven’t blogged for a while and I forgot how internet commenters can get bizarrely angry about statements like “I got tired of managing my vim config so I decided to stop using vim for now”, as if it’s some kind of attack on vim (or on them??)

It makes me really appreciate @grimalkina’s work on developer culture, like this https://osf.io/preprints/psyarxiv/2gej5_v2

I still have a lot to learn but her work has helped me start to understand where this stuff comes from

(I used vim for a long time and I love it!)

OSF

@b0rk @grimalkina I was astonished when I said in a talk that the C++ macro feature was bad and people got mad at me. I thought it was self-evident and that even big fans of C++ would agree with me that the macro system was one of the worst parts of the language.

Instead they just got angry.

@b0rk @grimalkina A while back I was helping my kid with her CS class homework and sent her a followup email observing:

“You lost a lot of time and energy dealing with issues like: Using vim; copying files back and forth with scp; losing the network connection; the college shared machine is slow and yucky.”

“It's important to remove as much friction as possible from your basic process. Otherwise it's like trying to cook with dull knives and rusty pots, except worse because it interrupts your train of thought. You can't do good work with bad tools.”

“When you start the next project, start it in VScode in the beginning. And maybe set aside an hour or two before you start in earnest, just to go through the VSCode tutorial and familiarize yourself with its basic features, without trying to do that at the same time you are actually thinking about your homework. This will pay off quickly.”

Then I published the letter on my blog and boy oh boy did I get a lot of hate from the vim fans.

But the simple fact was, she lost a lot of time and energy dealing with vim.

@mjd @b0rk this is making me feel great about working in VSCode lol

@grimalkina @mjd @b0rk I’ve been using vim since I was a kid. I have used it for a lot of projects over the years, professional and personal.

I don’t use vim for work anymore. I use the thing that will definitely work and is easy to get to a known good state. Vim is a great editor. But VS Code is the gold standard.

@b4ux1t3 @grimalkina @mjd @b0rk I've been using some form of vi (mostly vim) for nearly thirty years, and I still love it for tasks that only involve a handful of open files. But for anything larger I want a real IDE, and for the last five years that's been VS Code. The modern vim experience seems to start with installing and configuring a zillion plugins, and I just want an editor that basically works out of the box, to which plugins can be easily added if needed. That said, I'm currently trying out a vim-emulating plugin in VS Code. Not totally sure I like it, but it definitely makes some forms of text-manipulation easier.

@pozorvlak @b4ux1t3 @grimalkina @mjd @b0rk I regularly use vim, notepad++, and VS Code each for different reasons or to solve different problems. Lately gvim has been "helpfully" autoindenting and inserting [expletive] tabs into my text and I have not spent the time to figure out why this is happening or (more importantly) how to disable it permanently.

I have zero plugins installed; every time I look into vim plugins I waste 2-3 days trying to make anything work and the time spent is never worth it.

I was forced to use vi back in 1986 because the alternative was ex. Emacs was not available for some reason, probably due to limited disk space (it didn't seem like it at the time but I feel I dodged a bullet there...)

I find VS Code is good for complex projects, vim is good for precise bulk editing, and npp for when I want to just want to write without doing much editing.