I’m relatively new to programming, I’ve been learning C on linux using nano and it’s been very fun. I’ve recently fallen into the emacs/vim rabbithole and I’ve been watching videos about emacs, Doom, spacemacs, neovim and reading comments about people switching from this or that to another config or editor, and I’ve been a bit lost on what to do. Then I realised that I haven’t done any coding and spent all of my time focusing on editors. So here is my question (which has probably been asked many times) : what is the point of investing so much time learning all of this when there are some IDEs that are preconfigured with all the functionality a programmer would need ? Does learning neovim or emacs actually save time in the long run? I know that they’re much more lightweight than IDEs and I’ve been really enjoying using the terminal much more than my time on IntelliJ, but having an easy out of the box visual debugger, refactoring and jump into functions can be really helpful in the long run I think, especially when starting to write actual large programs. Nano is fun, but not a time saver. Why did you chose your editor?

  • @Teddly
    2•1 year ago

    This is exactly where I’m at. Learning vim binding has also opened me up to a lot of REALLY great TUI options. lazygit has become something I never want to work without again, and it’s only pleasant if you’re used to vim bindings. There’s also k9s and other great TUI tools out there that make learning vim bindings hugely worth it.

    But, after investing a week into heavily trying to get neovim working, I went back to VS Code w/ vim plugin. Still want to get neovim working for me at some point but will have to find time to do it without hurting my professional output.

    I will say so far the only pain point I’ve found running vim plugin in VS Code is missing ctrl/cmd + d… I used to use that a lot to do some really powerful multi-cursor editing and vim bindings ruins it. I actually went and disabled the vim plugin just to go do one thing with uninhibited multi-cursor a while ago, and turned it back on when I was done.