In my experience, there is a huge distinction between IDE (JetBrains products, Eclipse, Visual Studio [not Code], etc.) and code-editors or text-editors with extensions/plugins (VSCode, Sublime, Notepad++ at the end of the day, etc.).
We tend to look at this from our own personal experience in development and not from the perspective of the tool: IDEs are developed with a lot of research on what is good and functional in regards to DevUX (and these are not just common guesses from implementors, there is a lot of market testing, focus groups, etc.).
When we are talking about editors, they will solve that problem and stop there. Plugins and extensions are community additions to this ecosystem and they also solve their problem while often ignoring the ecosystem in which they will be run (i.e., compatibility between different plugins/extensions).
In IDEs these things are already considered and integrated with the feature.
It’s the same as using a framework vs building your own: you will get all the tools for the problems that you might not be solving now for the adequate cost (either physical space, code requirements or price) vs solving every "current" problem with some approach (either coding it yourself or pulling some library that will solve that problem while fixing potential non-compatibilities between libraries).
My personal favorite: JetBrains tools (any of them)
I shifted from using literally 10 different tools to a single tool (PHPStorm most of the time for both frontend and backend, switching to other tools is other backend language is used).
It has one of the most functional and simple-to-use integrated support for Git.
It has integrated functionalities of Datagrip for all database functionalities.
It has always up-to-date debugging toolsets for supporting languages (yes, even JS on both frontend and backend that links directly to the code).
It has integrated support for linting (ESLint), transpiling (TypeScript), library specific supports (React, Vue).
Plus the whole Performance management that will track your personal bettering with shortcuts and other available functionalities.
And recently they integrated Code with me functionality for easier pair programming together with voice and video chat.
And yes, it is "pricey" but considering how much time you might spend on installing and maintaining different extensions whilst possibly missing out some new great functionality just because you as a developer are not exposed to certain blog posts or communities, the price is completely all right. Also, if we in IT cannot spend ~$400/year for our toolsets, we are (in my opinion) doing something wrong. :))
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my experience, there is a huge distinction between IDE (JetBrains products, Eclipse, Visual Studio [not Code], etc.) and code-editors or text-editors with extensions/plugins (VSCode, Sublime, Notepad++ at the end of the day, etc.).
We tend to look at this from our own personal experience in development and not from the perspective of the tool: IDEs are developed with a lot of research on what is good and functional in regards to DevUX (and these are not just common guesses from implementors, there is a lot of market testing, focus groups, etc.).
When we are talking about editors, they will solve that problem and stop there. Plugins and extensions are community additions to this ecosystem and they also solve their problem while often ignoring the ecosystem in which they will be run (i.e., compatibility between different plugins/extensions).
In IDEs these things are already considered and integrated with the feature.
It’s the same as using a framework vs building your own: you will get all the tools for the problems that you might not be solving now for the adequate cost (either physical space, code requirements or price) vs solving every "current" problem with some approach (either coding it yourself or pulling some library that will solve that problem while fixing potential non-compatibilities between libraries).
My personal favorite: JetBrains tools (any of them)
I shifted from using literally 10 different tools to a single tool (PHPStorm most of the time for both frontend and backend, switching to other tools is other backend language is used).
It has one of the most functional and simple-to-use integrated support for Git.
It has integrated functionalities of Datagrip for all database functionalities.
It has always up-to-date debugging toolsets for supporting languages (yes, even JS on both frontend and backend that links directly to the code).
It has integrated support for linting (ESLint), transpiling (TypeScript), library specific supports (React, Vue).
Plus the whole Performance management that will track your personal bettering with shortcuts and other available functionalities.
And recently they integrated Code with me functionality for easier pair programming together with voice and video chat.
And yes, it is "pricey" but considering how much time you might spend on installing and maintaining different extensions whilst possibly missing out some new great functionality just because you as a developer are not exposed to certain blog posts or communities, the price is completely all right. Also, if we in IT cannot spend ~$400/year for our toolsets, we are (in my opinion) doing something wrong. :))