Coders or lemmy, what editors do you use? Is it worth learning a new one?
-
vi WAS almost ubiquitously installed on any host you’d connect to, so it was worth learning.
The reason we like it is because it’s been iterated over to be useful for modifying the types of files you’d be editing. It has a significant plugin ecosphere and does its job well.
For editing on remote computers I use VSCode remote or Micro for quick tasks.
and vim is the 10k amp in your analogy … huh.
-
I swapped to neovim 10 months ago. Haven't looked back. Actually, I've looked back a LOT for the first few weeks because I couldn't figure out how to do certain things. But the more you learn the better it becomes. Not needing your mouse is SO good.
-
I started with neovim because I hate my laptop's mousepad, and that's often pushed as a benefit of modal editors, not needing the mouse. After I used it for a while I found that not only could you do stuff that you could do stuff easily that would be difficult in, say vs code, but it was also pretty fun. It's honestly a bit of a power trip sometimes, makes me feel like a 90s tv hacker. Also plugins. So many neat plugins.
-
I'm still learning to code, but I tried out a bunch and I've liked using Vim, VScodium and Pycharm.
-
-
I use emacs when on my personal machines. VS Code at work.
The fastest tool is the one you are best at using. I find that my tool doesn't make me fast, my ability to solve issues makes me fast. I very rarely learn a new tool unless it accomplishes something for me my other tools do not.
For example, at work I use windows and regularly ssh to servers. My entire job is spent ssh'd into other servers. Emacs terminal emulator is spotty at best when using ssh on windows. There are ways to make it work, but some modifications get flagged by our SEIMs. So in that case I use vs code, and the ssh remote connection options and split terminal interface.
At home I use emacs. I have all Linux machines so my terminal plays nicely. I also am working on reducing my RSI from years of tech work. The less mousing I have to do, the better. Emacs allows me to keep my hands on my keyboard.
-
I used to use VSCodium, but in my quest to touch the mouse as little as possible I switched to Neovim.
-
I've mostly just tweaked the configuration and built my own comment formatter/reflow command based on the comment style at work.
It's almost more about what it doesn't have for me, because what I've run into a lot with trying newer editors is they try and manage the code too much and the code base at work has its own style guide that doesn't match what the editor tries to do. So the editor might make me slightly more productive ... until I find myself fighting with it every 3 lines because of auto formatting or some language server quirk.
-
I use Lapce, which could be a great native alternative to VS-Code
(Also it's built with Rust, this is for the Rustaceans) -
Did you mean Visual Studio the second time?
-
I left a comment before but I thought I'd address the concerns around modal editing. It's not as hard as it seems, once you wrap your head around hjkl you'll be fine.
Use Lazyvim to get started and install the vim plugin in vscode. Try it qutebrowser too you won't look back honestly.
Consider helix too, it works out of the box but the keys are slightly different to Vim which makes it challenging for me.
-
I use VSCodium atm.
-
Neovim genuinely makes me happy. I love it to bits.
-
this, evil is the real 4th generation vi
-
vscodium. Easy to use for beginners (i'm a beginner too), fully open-source, all microsoft tracking binaries removed. Aviable for Windows, Linux, macOS, darwin, propably bsd, or even as a webview, and supports a lot of architectures. Great for intrepeted languages, but supports compiled ones too
-
Zed, Helix, and VSCodium for the Windows side.
-
Helix because it's easy to setup and hassle free, and it runs well on my 2009 ASUS Eee
-
vscodium and neovim extension
-
i really wonder why mousepads sucks
-
