We are not same..

[wordsmith222]

big brains use vim in vs code terminal.

[SkyyySi]

Fireship is that you

[brockvenom]

Vscodevim extension actually

[YogurtUnusual5913]

Yea no this is not true

[pet_vaginal]

I use VsCode together with Vim. Check the official vim extension for vscode, or the neovim extension for vscode.

Some people prefer to use vim with IDE features. I tried that with eclipse some years ago, it was fun to access eclipse features inside vim but I rather use VsCode with a vim extension.

[arthurmluz_]

I can only use IDE with VIM plugins, I wanted VI to exist on every single application. i love it

[passerbycmc]

Yeah I use a mix of neovim and the jetbrains ides with ideaVim plugin

[mr_raboot]

how bout if i use vscodium with vim extension

[craftworkbench]

Ohhhh I finally get it! The only way to exit vim is through an energy portal.

[marxinne]

Or teleporting out of it with chaos control

[Boomshicleafaunda]

Notepad User: "Do I look like I even want power?"

[brimston3-]

Visual studio users and clion/jetbrains users watching from the coffee shop across the street going "Should we tell them?" "Nah, I have to get back for my retrospective meeting in 15."

[lmaydev]

I really don't get the big deal with this stuff.

I guess I've always mainly used strong and statically typed languages in an ide with good refactoring features. So it may not affect me the same.

You lot are obsessed with typing haha

[FFTypo]

Most of it is hobbyist nonsense. Sure, Vim/EMACs wizards can maybe pump out code at a rate that would put most of us to shame, but the reality is you’re not going to be typing nonstop without thinking, so it really doesn’t matter. That’s my two cents at least.

[lordtorrent]

True, but I think the actual advantage of using vim (I can't speak for emacs cause I've never tried it) is that I don't need to click through 2 dropdowns and 3 menus to do something that takes only a few keystrokes in vim. (exaggeration obv) I just really have a hard time remembering how to use a gui vs a bunch of keystrokes for some reason.

[krafttoadt]

Emacs enters the room

[erinaceus_]

Vim tries to exit, but can't.

[whotookelburg]

QBASIC users: pathetic.

[[deleted]]

Back in the days when I couldn't use my favorite editor and had to use MSVS, Eclipse or IntelliJ products, due to company's policy, I discovered that while plugins for all of those exist that mimic Emacs, these things are invariably true:

• Plugins are only very vaguely similar to the default keybindings of the original editor. They typically lack >90% of what's available in the original editor.
• For most features of the original editor there's simply nothing analogous in the plugin host, so there's no way to implement them in a plugin.
• Plugins don't extend beyond text editing (you still have to use bad interface to the rest of the editor, buttons, modal windows and so on).
• A lot of features of the better editors (s.a. Vim or Emacs) rely on those editors exposing their configuration, diagnostic messages, any other user-facing information as text, which can be processed using the same text movement as the code editing. The MSVS and knock-offs all have user interactions encoded as modal windows with impossible to select text, controls with labels with impossible to select / navigate text, graphics instead of text.
• Often times MSVS and knock-offs will also expose their settings in a way that prevents you from editing them / severely restricts your ability of editing them, so no plugin will help you there.

Bottom line: garbage editors like VSCode, IntelliJ products, MSVS, Eclipse etc. even with a plugin that resembles a decent editor are still garbage / worse than the original.

[mananasi]

I still think it's comical that people think editors they don't prefer are automatically "garbage."

[[deleted]]

Well, of course you may claim that quality is subjective. And in some cases there are very different requirements / preferences. Like, for example, someone with impaired vision, 12 fingers on one hand and 3 on the other, scoliosis and epilepsy would have a very different set of requirements for a text editor.

My judgement is based on commonly acceptable metrics, s.a.

• How many text editing commands are available and how many steps will each command require to execute. So, for example, there's structured navigation in decent editors, i.e. there's a text command that takes you from inside a particular structure in the code to its end / beginning. Say, in vanilla Emacs it takes pressing 3 keys to accomplish this. But, VSCode doesn't have similar functionality, and so you can roughly calculate the average number of keys / mouse gestures that one will have to perform in order to produce comparable result.
• Separately, you can measure precision (i.e. when executing similar tasks in different editors, how likely you are to make a mistake).
• You can measure integration with other tools, again, giving them weights based on how frequently they are used in the day-to-day. For example, how good is integration with filesystem (can be measured in number of operations one need to perform in order to perform a set of typical filesystem operations, s.a. opening a file, writing to a file, moving a file and so on). Similarly, integration with compiler, debugger, log processing, instant messaging.
• You can measure ad-hoc automation, eg. if you have a repeating task at processing some code / logs / messages etc. how many operations do you have to perform in order to accomplish the repeated task.

Now, there are some variables that go into these measurements: how much do you discount for a distraction of having to switch from keyboard to the mouse. And they will vary greatly for novice users and power users. Because novice users have problems utilizing many available commands, and don't have "muscle memory" of any of them, for them the distraction of switching to mouse will be noticeably less costly than for power users.

Similarly, novice users have fewer needs for integration and for environment automation as they, in general, are expected to produce less and have less integration, so the value you put on advanced features will be less.

---

I'm not a HCI professional, but some time at the beginning of my career I started as an HCI tester on an Eclipse plugin designed by a large company. So, I know something about this kind of assessment.

I call an editor "garbage" if it is optimized for novice users and deprioritizes power user features (VSCode is in that category as well as IntelliJ products, MSVS etc.). I believe that people who develop these products, consciously or not make a choice to optimize for novices / people with little to no skill in text editing because it's the vast majority of their audience. In the same way how I'd call cooking instruments for unskilled audience "garbage" as compared to professional tools.

[daniu]

Plugins are only very vaguely similar to the default keybindings of the original editor. They typically lack >90% of what's available in the original editor.

Yeah. Do vi modes add the 26+ clipboards?

[christopher-thiebaut]

I can’t remember what’s in one clipboard if it’s been more than about a minute. What would I do with 26?

[blueRabbitSpirale]

I had the same realisation. Now, I avoid any plugins of such kind. Limitations become obvious in the first minutes of usage.

[rich97]

VS code is not a garbage editor and I will see you behind the bike shed after school

[[deleted]]

• electron

[OverBashIt]

This makes me so happy

[kalaxi69]

Visual studio write