Vim, nano, micro, emacs… ffs. Your text editor should not be a shell, a file manager, a compiler, a build system or a dependency manager. Do one thing and do it well, a editor that tries to be everything ultimately becomes an inflexible mess. An integrated system often becomes an interdependent system, where you are stuck with a single build system, version control, compiler, or file manager. When these are separate tools, they are interchangeable, one person can use vim, the other nano, a third gedit. One project can use make, a second ninja or meson.
If a project uses VScode, it basically forces everyone else to use it or forces you to maintain two separate build systems. Another option is to only use external tools, but then VScode just becomes an extremely bloated text editor. On my computer, both vim and emacs, start before I can lift my finger from the enter key. The same can’t be said about VScode.
I’m all for using vim or Emacs or whatever, and I agree that not having a dependency on a specific editing software is a great thing.
But since when did using VSCode enforce the decision on other members of the team? VSC is just going to integrate it’s features with whatever build system you are using. It doesn’t enforce any particular build tool in any project. You can use NPM, yarn. PNPM, whatever the fuck else lol… Nobody needs to maintain multiple build systems to support VSC because it is also just a text editor, albeit a bloated one. Yes, if you install all the fancy extensions to integrate VSCode with your project, it will be a heavy app, and that’s a problem. But if you want your barebones editor, just don’t install any extensions? I’ve been in projects where I’ll be using VSC while someone else will be using Vim and that one dude will be using webstorm or something. It works. There is no MicrosoftTM build tool lockdown going on.
I know vim is still far less resource intensive than code but outside of very specific use cases, I’ve never seen any modern computer struggle with running code, especially without the extensions… It’s equivalent to opening an extra chrome window, I’m sure most computers can handle that lol.
End of the day the best tool is whatever lets you personally write code faster, and for some of us that happens to be VS Code
Vim, nano, micro, emacs… ffs. Your text editor should not be a shell, a file manager, a compiler, a build system or a dependency manager. Do one thing and do it well, a editor that tries to be everything ultimately becomes an inflexible mess. An integrated system often becomes an interdependent system, where you are stuck with a single build system, version control, compiler, or file manager. When these are separate tools, they are interchangeable, one person can use vim, the other nano, a third gedit. One project can use make, a second ninja or meson.
If a project uses VScode, it basically forces everyone else to use it or forces you to maintain two separate build systems. Another option is to only use external tools, but then VScode just becomes an extremely bloated text editor. On my computer, both vim and emacs, start before I can lift my finger from the enter key. The same can’t be said about VScode.
Emacs
Emacs
I’m all for using vim or Emacs or whatever, and I agree that not having a dependency on a specific editing software is a great thing.
But since when did using VSCode enforce the decision on other members of the team? VSC is just going to integrate it’s features with whatever build system you are using. It doesn’t enforce any particular build tool in any project. You can use NPM, yarn. PNPM, whatever the fuck else lol… Nobody needs to maintain multiple build systems to support VSC because it is also just a text editor, albeit a bloated one. Yes, if you install all the fancy extensions to integrate VSCode with your project, it will be a heavy app, and that’s a problem. But if you want your barebones editor, just don’t install any extensions? I’ve been in projects where I’ll be using VSC while someone else will be using Vim and that one dude will be using webstorm or something. It works. There is no MicrosoftTM build tool lockdown going on.
I know vim is still far less resource intensive than code but outside of very specific use cases, I’ve never seen any modern computer struggle with running code, especially without the extensions… It’s equivalent to opening an extra chrome window, I’m sure most computers can handle that lol.
End of the day the best tool is whatever lets you personally write code faster, and for some of us that happens to be VS Code
(Neo)vim