Comment by arw0n

Comment by arw0n 5 days ago

3 replies

> MANDATORY: Get more intimate with my Neovim. I've always kind of half-arsed my editors / IDEs, I always found it annoying to become a deep expert. This must change; surface-level skills rob you of productivity.

I'm actually not that convinced of these productivity gains in the context of IDE tricks. The cost of learning + tool-lock seems steep compared to the actual productivity gains. I'm switching fairly regularly between IDE's, and even if VS Code is the default, the only reason I'm considering learning it in depths is because some people incessantly comment on these things during pair programming.

manuel2258 5 days ago

I'm in the same boat as the parent with helix. I like to think that its not about being able to type x chars more per second but rather doing some clever tricks sometimes with your IDE just because they safe you from boring work and is lots of fun. For example repeating the same action with macros across multiple files is so helpful and maybe only needed once a month or so, but oh boy, when you pull it off it is so fun and rewarding!

skydhash 3 days ago

I’m used to both vim and emacs. While I appreciate some IDE power features (debugging, code generation, tools integration,…), ultimately editing is very much a chore with them. You could add emacs or vim keybindings, but then you start to miss some of their features.

But whatever the editor/IDE, There’s always some neat tricks that will help you, especially around editing and tools integration.

pdimitar 5 days ago

I get your point but I am fairly sure I'll never move away from Neovim or nano (when I really have no choice).

There are Zed and Helix of course and they are on my radar but... not enough focus and energy for such big quests.

As for speed, I know Neovim can do much more than I use it for and I want the speed. When I can code even quicker my thought just flows through my fingers and the result is always good. But I have not been like that for years (ever since I gave up Emacs) and I want it back (and no I wasn't that much faster with Emacs either).