4 ms·
Definitely not the same effect. The vscode application is much nicer than a terminal, has lot of plugins that I'm not sure exist for vim. And you can disable te
by elcomet 4y ago
Definitely not the same effect. The vscode application is much nicer than a terminal, has lot of plugins that I'm not sure exist for vim. And you can disable telemetry. And it's much faster to learn
- iillexial 4y agoI feel like Vim has more plugins than VSCode
- elsjaako 4y agoNothing wrong with your setup if you like it, but I'm very curious what features you are missing in vim. Can you give any examples?
- elcomet 4y agoThe learning curve mostly. And most things you need are there out of the box, or very easy to install. Also plugins like remote ssh. Overall it just works without too much effort.
- elsjaako 4y agoRemote ssh is built into vim. I think it's formally a plugin, but it's installed by default. Of course, if you don't use too many plugins, vim is also designed so you can run it remotely. I use this sometimes to have a long-time running vim session on a remote server, using tmux or screen to reattach when I log in.
- quickthrower2 4y agoIronically I find using a terminal inside VSCode horrendous. And since most times I need to open 2-3 of them, I have a much better experience with one terminal outside of it, and tmux. And if you haven't tried it, use tmux. It is the geeky tool that unlike vim/emacs you can learn in 60 seconds and immediately adds value. Whereas vim/emacs take longer to learn and get a payoff - I never managed to get to that part of the curve. Add another 5 minutes to set up a tmux script for your development workflow!