• pinball_wizard@lemmy.zip
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    Everything you can do in VIM, you can do in VSCode running VIM in a terminal, but not the other way around.

    You would sure think so, right?

    But the VSCode plugin ecosystem still lacks some features available in the Vim ecosystem, and (fl just for example) LazyVim has most of the features available in VSCode.

    At the end of the day, the biggest difference is speed. Even very brief unexpected delays can break my concentration. While VSCode is no slacker, it still has some delays, probably mainly because it’s still JavaScript under the hood.

    Once there’s a GoLang, Rust or C port of VSCode, I may well switch permanently.

    • masterspace@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 days ago

      But the VSCode plugin ecosystem still lacks some features available in the Vim ecosystem, and (fl just for example)

      Isn’t that basically the same as Command Shift P and / or the search feature?

      At the end of the day, the biggest difference is speed. Even very brief unexpected delays can break my concentration. While VSCode is no slacker, it still has some delays, probably mainly because it’s still JavaScript under the hood.

      Once there’s a GoLang, Rust or C port of VSCode, I may well switch permanently.

      I can 100% understand how big of a deal speed delays can be, but at the same time, not to probe too hard, but what are you experiencing delays in? In all honesty waiting for ohmyzsh to start, or waiting for a git pull to run, takes far longer than any task I can think of in VSCode. Files open faster than notepad, the file browser is fast, the shortcuts and commands are fast, I honestly haven’t experienced any slow downs with it anywhere, and I’ve used it with monorepos that are TB in size.