Well, this is my friends and me in my early 20s. The only true way is to use vim/emacs, CLI tools for everything. GUI is for losers. And the only TRUE and SERIOUS languages for COOL KIDS are C++, Haskell, and Perl. If you don't use them, you are code monkey.

And here I am, doing everything in typescript for my job, use VSCode and Webstorm, in love with GitKraken. What a shame. I'm not a cool kid anymore.

Apparently, VSCode is considered a text Editor. And i mean, if you played with Netbeans and Eclispe, and are now working with VSCode, this whole thread would seems a bit weird to you.

The main difference i see between Text editor and IDEs: with text editors you need to add your own configuration and tooling, and this can takes time, while with IDE everything is already in and you just need to learn the quirks.

But right now, i'm working to integrate programs with OCS pods and weird network architecture (we can only interrogate some APIs from the Openshift cluster as a security mesure), and my collegues who only ever worked with IDEs have a development cycle that look like this:

Write code => push => build new image=> deploy pod with new image => get the input and correct mistakes => repeat

I just work withing the pod (i use vim because its everywhere, but i could build the pod with VSCode inside, it is light enough).

So i'll say this: imho if you're in for a short-term contract, learn to use you employer IDE. If you think you'll stay a long time AND you like to have tailor-made tools for you, you can consider a text editor. Whichever choice you make, always learn a new language with the least tooling help you can get (in Eclipse you can deactivate stuff), and learn ed or Vim if you might go DevOps in the future.