Exactly this. Don't blame the airplane for not being a car, or a submarine for being a beach buggy.
Obviously people have made things for VIM to be IDE like, some are cool to me, but completion-integrations-lang-servers always seemed so anti-vim to me. Make an HTTP request every key stroke to get suggestions? The. Latency.
VSCode does the same. And it has nothing to do with HTTP (not by default at least).
No, Vim can be an excellent IDE. Just not a "works out of the box" one.
Re:LazyVim
by yodsanklai on Monday July 17, 2023 @06:54AM
(#36756429)
on the other hand, using vim mode in vscode let you use vim where it shines: modal editing. It's the best of both worlds.
Re:LazyVim
by johannboehme on Monday July 17, 2023 @08:06AM
(#36757183)
not really..
vim is easy to extend and adapt.
You loose that with only vim mode in vscode.
You also loose the ecosystem and relevant core functionality like most vim core functionality like :grep :vim :make, quickfix list, arglist etc..
Then tell the vim fan bois to stop telling people to use vim as their ide....
The issue isn't with the fact people try to use it that way, it's that those who use vim are adamant it's the best option for doing so and berate the Other until they try.
I don't think vim is meant to be an IDE. If you want an IDE, go get an IDE. If you want a text editor, vim works well. But vscode is unwieldy as a text editor, and vim is painful to contort into an IDE.