I get that portability makes sense if you're shipping a software but how many different uncontrollable environments are you going to face? It's usually only a few environments that's under your control.
> VS code doesn't let you sync configs
I thought it's just a JSON file.
> It's a blazing fast
This depends, if you make your vim full blown to match the feature (which is probably not even possible), vim tends to start up pretty slowly.
Vim key bindings are pretty much available on most editors out there.
And you'll be losing so much from the vast list of plugins available in vs code.
You can't autocomplete table names in SQL strings like in JetBrains, I've quit using vim 15 years ago as my programming editor.
> I get that portability makes sense if you're shipping a software but how many different uncontrollable environments are you going to face? It's usually only a few environments that's under your control.
At my day job and for my personal infrastructure, I routinely edit files across a wide variety of shuffling environments. I am a pentester by trade and also enjoy homelabbing, embedded systems, and working on my ADHD-fueled inventory of fun projects. I am not a dedicated software engineer that has to write polished production-quality enterprise applications. All my shit is held together by duct tape and bubble gum. I 100% understand why you'd want a beefy dedicated IDE for a product you're working on full time.
> I thought it's just a JSON file.
If VSCode has changed in the past couple years to json file that's great! But last time I tried I wasn't able to move around my config easily without signing into some web service.
> This depends, if you make your vim full blown to match the feature (which is probably not even possible), vim tends to start up pretty slowly.
Absolutely right! I keep my plugins minimal. You can do almost everything the plugins can with vanilla vim.
> Vim key bindings are pretty much available on most editors out there.
Also true! In my experience, its wonky and usually requires YET ANOTHER plugin. They're never at parity with all the vim actions.
> And you'll be losing so much from the vast list of plugins available in vs code.
> You can't autocomplete table names in SQL strings like in JetBrains, I've quit using vim 15 years ago as my programming editor.
That's also fair, but I don't use most of those plugins. Only copilot (also available in nvim) and remote editing really amazed me from VSC. Everything else I can just do myself by spawning a shell, using pipes/redirects, and unix tools. For example, I don't need GUI elements for git baked into my editor...I just use the cli.
You can definitely autocomplete SQL table names, but it would require some manual configuration. My autocomplete mostly pulls from strings in my open buffers.
I'm not arguing that any either approach is inherently better, just stating my preference. And for the original topic of remote editing ssh+vim is my preferred solution. Absolutely language-specific IDEs have major benefits over a general purpose editor.
There's also the FOSS philosophical argument but that's just a personal belief and really doesn't matter for all practical purposes.
> VS code doesn't let you sync configs
I thought it's just a JSON file.
> It's a blazing fast
This depends, if you make your vim full blown to match the feature (which is probably not even possible), vim tends to start up pretty slowly.
Vim key bindings are pretty much available on most editors out there.
And you'll be losing so much from the vast list of plugins available in vs code.
You can't autocomplete table names in SQL strings like in JetBrains, I've quit using vim 15 years ago as my programming editor.