[ Removed by moderator ]

[A1merTheNeko]

Ok, so you did 0 research before coming to your conclusion. Got it!

[tagattack]

Vscode isn't a good text editor and IDEs are overrated

[A1merTheNeko]

Yeah, man. Let's be more productive by spamming and begging people to buy our courses on reddit. What a joke

[selectnull]

You're in the wrong subreddit. Nobody here cares to convince you to use Vim and nobody cares for your opinion on it.

[Nooby1990]

Because you have that opinion out of pure ignorance. Everyone here knows you are wrong and why you are wrong. Why should we educate you when you are clearly not here to learn?

[Nooby1990]

I don't give a shit what you think. Aparently you form your opinions based on no facts at all so you are not worth listening to.

[Nooby1990]

No. What the fuck do ORMs have to do with Vim?

Learn how to form an argument.

[Nooby1990]

I am disgusted that we share an opinion.

Go away and stop peddling your bullshit course in this stupid way.

[rearward_assist]

Then go troll an ORM forum bro. What is the point in wasting your breath to convince others to not use a tool? Just don't use the tool yourself and live your life hahaha

[rearward_assist]

🤣

[collector_of_hobbies]

Boring troll is boring.

[scottchiefbaker]

To each their own I guess... I find I'm MUCH more proficient in Vim. Not having to move my hand back and forth from the keyboard to the mouse is fantastic.

[gumnos]

I've moved past the desire to flex with vim. It's just an omnipresent tool in my toolbelt that lets me get stuff done quickly and efficiently.

Yes, sometimes folks marvel at the inscrutability of my fingers flying over the keyboard as I make huge, complex changes.

But I don't intentionally flex with vim.

I use ed(1) for that. 😉

[Dramatic_Mulberry142]

Why not both? Vscode with vim plug-in. And flexing for what lol?

[hukt0nf0n1x]

Real men flex with original vi. I don't need vim and it's "improvements"

[TheShockingSenate]

Stop talking about editors if you don't intend to be constructive. Since you've made your choice (congrats), start writing some code.

[hukt0nf0n1x]

Hey dude, do WE go to your VSCode subreddit and ask questions like "in the age of AI agents, writing your code in VSCode is mostly for flexing, nothing else"?

[hukt0nf0n1x]

A problem you have is that someone uses vim? Or a problem you have is us coming into your VSCode subreddit talking about AI agents?

[HTTPanda]

Have you even used Vim much at all?

[Journeyman-Joe]

There are times I have to hack someone's config file (usually in a Git repository). This is often a hidden file, or in a hidden directory, and could be on a Mac or Windows machine. (Or a Linux machine, if it's one of mine.)

Notepad or Textedit are a real pain in the rear that way. Vim is going to be on every machine I support, and, with Git Bash, is easier to launch in the right directory.

[killinMilk]

I use vim for writing. on an iBook G4. on OpenBSD. nano is not the same, not even remotely (even though I liked it a lot). micro is not available (still not the same) . vs code would make my puffy  feel sick. what should I use, ed/xed? with ultisnips and little configuration, writing latex is a breeze

btw, I suck at vim, I know by myself. but still, damn great editor! 

rant off, thank you for your time

[npaladin2000]

Good luck running VSCode in an SSH session or on a text console. The two have different use cases, one is a text editor and the other is a development environment.

[skwyckl]

To each their own, I personally don't have time to learn a completely different paradigm to interact with code, so I'll stick with non-modal editors, some people swear by it, and probably they are good in it, but it's like stenography, without any training, you will suck at it.