Because IDEs are opinionated, and devs love customization and control.
I use a few of the Jetbrains IDEs every day, and I consider a "full IDE" a necessity when working on a large complex codebase.
But my frustrations still stand: IDEs can be slow, bloated and buggy, and it's often difficult to get things working exactly to your liking.
So I fully understand that those working on nicely separated JavaScript components or a single Python script choose VSCode, Atom or Vim — I personally don't find it viable though when working on a large & sometimes messy backend framework.
Because IDEs are opinionated, and devs love customization and control.
I use a few of the Jetbrains IDEs every day, and I consider a "full IDE" a necessity when working on a large complex codebase.
But my frustrations still stand: IDEs can be slow, bloated and buggy, and it's often difficult to get things working exactly to your liking.
So I fully understand that those working on nicely separated JavaScript components or a single Python script choose VSCode, Atom or Vim — I personally don't find it viable though when working on a large & sometimes messy backend framework.
In these environments, I sometimes would choose such a tool as well. “Right tool for the job” as they say.