I'm being condescending lol? No u 😁

Just to chime in with my own opinion on JetBrains' tooling, my first language was Java - admittedly its been a while since I tried Java (and other JVM languages like Kotlin) in VSCode but when I last did it was a bit of a challenge. I also did some Android development for a while and if "standalone" Java was awkward in VSCode I assume Android development would have been too (Android development in general was nightmare fuel until Android Studio came along, never really did like Eclipse all that much).

After expanding out into other languages, I have enjoyed the specialization of each of the JetBrains IDEs. VSCode always felt like a "Jack of all trades, master of none" type of experience for me personally. I have tried out Zed recently and while I think its going to be a decent editor, I still have similar issues with it that I have in VSCode (in that how well it works depends on what language you're using).

The exception to their tooling that I haven't really liked though is Fleet - which was their answer to creating an equivalent to VSCode. It hasn't really seen a lot of development and feels more like the forgotten step child of JetBrains. Also the "Remote Development"/JetBrains Gateway features can be really hit or miss though thankfully I don't need that sort of functionality often.

On mint it actually finds the C# sources in Godot, for example. It also easily "compiles" and launches the soft through Godot, with working debugging. Vscode is a nightmare to set up, there are configs, other files, project files, and other parameters that just aren't taken into account. Or having, gasp, code in a folder, it just isn't getting scanned by vscode. You can surely get it to work, but if you don't use the base boilerplate setup it just doesn't function well at all.

I have used visual studio since early 2000 and it was good, then it became bloated, and vscode is IMO just a lighter version of that bloated visual.