Tech Versus: Vim vs Visual Studio Code

Recently I saw a lot of tweets talking about Visual Studio Code versus Vim. Should I use vs code or vim?, Vim is better, vs code is better. Vim masterrace, Vs code masterrace :) and so on so forth.

Everyone generally have a valid point of view, but I decide look a bit into it. So I decide to create this video. I go over on few different aspect of both Visual Studio Code and Vim. I also include my personal preferences about them, so they might become helpful too. I hope you've liked it, and as usual if you have anything to add or want to correct feel free to mention it in the comments down below :)

Socials:

#VisualStudioCode #Vim #TextEditor #TechVersus #MrRandomGenerator

*Logos used under fair use. Neither this video not the creator has any relation with the companies.

Memes
––––––––––––––––––––––––––––––

Music Used
––––––––––––––––––––––––––––––
Ghostrifter Official Social

[zeocamo]

2:33 is not a problem in Vim, there is a build-in file tree just like vsCode and there is a lot of plugins that help here too, if you add "fzf" you got a fuzzy search there is fester then any other search in other editors, and "fern" is a file tree that got all the features of a file manager, if you watn more then you can get LF or ranger to start in side of vim and use them, and Vim is not make with html, css and JS, and is so fast, and you can open big files in Vim, you can't in vsCode after 8000 lines and it begin to die.

ps. NeoVim is the best Editor

[engboy]

When you watch someone who know how to use vim properly it looks like they have superpowers. I have always wanted to get better at vim but I just use vs code because its easy

[YolunSonu]

If you are not started with Vim, Vscode is definitely the winner here. Because the amount of time you require to get used to Vim is too much, that in the same time you can learn many more shortcuts in Vscode, even you can add your own shortcuts. The power of Ctrl + Shift + P is phenomenal. The only advantage I see in Vim is when some people are watching you code, you look like a magician. On the other hand, Vscode is more than a text editor depending on your case. You can use it as a git UI, debugging tool, markdown preview viewer and so on.

[Trollend]

VSCode is the hands down winner. There is nothing you can do with Vim that you can't do with VSCode, but there are many things you can do with VSCode that you can't do with Vim. VSCode has intellisense, built-in debuggers, autocomplete, mouse-over documentation, source control manager integrations (Git, SVN, etc.), and thousands of integrations with other programming languages and frameworks. And while yes, Vim has plugins for some of those things, they are not nearly as easy to install or work with as it is for VSCode, and if you install enough of them they will conflict with each other.

The only category Vim wins in is that it doesn't require X11 forwarding if you're working on a remote server.

[jpjph]

As you said at the end, I will only use Vim in a terminal where I am sshd and basically out of options lol 😂

[nishanths]

Finally the winner is

1. Vim
2. Vs code

[metal]

Vim plugin IN vscode, that's the key

[telepenu]

bu ses tonunu nerde duysam anlarım.%100 türk :) arada türkçe içerik de yapsan iyi olur bence. mesela vim neden çöptür gibi :)

[AllwinJeba]

vs code is easy and straight forward.. specially debugging capabilities it brings it. I understand if you are in 1990 why one would prefer VIM. But now it just feels forced. Programming also includes a lots of browsing stack overflow and reading api documentation etc.
I would pick vscode anyday. If you want to show off then that's a different story..

But vim can be great for distraction free content writing like blogs or novels etc.

[Ginger_Hrn]

Nah bro real programmers use Microsoft powerpoint

[techsauce]

Vscode is all-in-one ...!
Modern IDE are good, don't know y people still use emacs or vim

[BeatSyncBytes]

w to move forward and ciw to edit the words in vim is just 🪄 magical. VIM is the ultimate katana I believe. I also like intelliJ idea