So when I'm coding C there's basically two things I find acceptable:

1. "I'm an IDE, don't worry about all that pesky command line stuff, we've got a nice GUI for you to set everything up like you want :)"

2. "I'm a shell. Use the command line if you wanna compile C. Fuck you"

The reason I hate Visual Studio Code is that it pretends to be #1 but in fact expects you to still know all the command line crap. But it doesn't stop there! Because even if you know the command line way of doing things is adds a layer of proprietary bullcrap between you and the compiler into which to pour your command line knowledge and no, fuck you vscode, I'm not going to learn a third layer just because you want to pretend to be a real IDE even though what you actually are is an overgrown fucking text editor

@eniko VS extends this problem to project files. "Oh look there's a friendly GUI to edit the project sett... right here's a recipe for how to hack the XML to do <anything advanced>. Good luck debugging it."
@eniko I was indignantly on your side until "overgrown fucking text editor" made me start giggling, I'm still on your side, but it's much funnier now :)

@eniko

I keep it installed, but I also have VSCodium installed.

Thing is that as far as I can tell and I could be wrong, the only other IDE that isn't a terminal app like VIM is Eclipse.

@eniko All good points, however my main reason for hating VS Code is simply that scrolling starts lagging when it has been open for a couple of days >_> it'll start out nice, scrolling at 120 FPS as you'd expect on a 120Hz screen, but then if I haven't restarted the editor between days it starts chugging, without even having big files open

I mean it's a TEXT EDITOR. Scrolling through text files is its ONE JOB. It can't even do that right.

@eniko till date I don’t know why I learnt that language