Spoken like someone who knows absolutely nothing about vim/unix.

Or maybe...hear me out...different people like different things. Some people don't like GUIs and enjoy working in the command line. For some other people, it's the opposite.

It's just different preferences.

You are making prejudiced, generalized, assumptions and presenting them as facts.

You are at best naive if you think people use vim and a terminal instead of "better graphical alternatives" (which there are none of if you've really gotten into vim/emacs/whatever). And we don't do it to seem hardcore (maybe we are, but that's a side effect). Software in the terminal is often more simple to use, because it allows chaining together outputs and has often simpler user interfaces.

The second paragraph is word salad. Developers should name their shit properly regardless of editor and it's quite simple to have a professional dev setup with 'intellisense' and auto complete in neovim. In fact, vim/neovim and I assume emacs too have much more features and flexibility of which users of IDEs or vscode wouldn't so much as think of.

I assume your prejudice comes from the fact that vim is not a "one size fits all no configuration needed" integrated development environment (IDE) but rather enables the user to personalize it completely to their own wishes, a Personalized Development Environment. In that regard, using one of the "better graphical tools" is like a mass produced suit while vim is like a tailor made one.

Just let people use what they like. Diversity is a strength.

You know neovim can use the exact same LSPs (Language Server Protocol) for intellisense as VS Code right? There's intellisense, git integration, code-aware navigation, etc. Neovim can be everything VS code is (they're both just text editors with plugins), except Neovim can be configured down to each navigation key so it's possible to be way more efficient in Neovim. It's also faster and more memory ~~edficient~~ efficient because it isn't a text editor built on top of a whole browser engine like VS Code is.

I use a Neovim setup at home (I haven't figured out how to use debugger plugins with Neovim and the backend I work on is big enough that print debugging endpoints would drive me insane) and I can assure you I have never given variable names one letter unless I'm dealing with coordinates (x, y, z) or loops (i, j) and usually in the latter scenario I'll rename the variable to something that makes more sense. Also, we don't do it to seem hardcore, it's because there are actual developer efficiency benefits to it like the ones I listed above.

By your own logic you "can't be bothered" to learn how to edit a single config file on a text editor that has existed in some form for almost 50 years (vi). Stop making strawman arguments.

I tried using VScode to play around with Golang. I had to quit coding to take care of something else. I hit save, and suddenly I have way fewer lines of code. WTF? Why did/would saving delete code? After much digging, it turns out because the all knowing VSCode thought because I had not yet referenced my variables, I never would, and since my code I wanted to save and continue later wouldn't compile, it must be quelled. Off with its head!

Anyway, I decided to use vim instead. When I did :wq, the file was saved exactly as I had typed it.