In that case every IDE is “just a text editor” because basically every IDE is built around modularity in this same way. This is just nitpicking over what is preinstalled.
Eclipse, visual studio, pycharm, idea… Those are full blown IDEs. They come with all the extras. All the text editors that can become IDEs have extensions or plugins that enable what these other actual IDE do natively.
Nowadays using vscode to debug a running program is common, but that was something only restricted to full blown IDEs some years ago, I’d say that vscode is lightweight IDE that can be expanded, but vim is a text editor first and foremost. You can’t really debug code in vim AFAIK, the most you get is syntax highlighting, linting, automatic whitespace removal and auto formatting? Not sure about the last one.
Sure, and VSCode without any plugins is a text editor, not an IDE.
In that case every IDE is “just a text editor” because basically every IDE is built around modularity in this same way. This is just nitpicking over what is preinstalled.
Eclipse, visual studio, pycharm, idea… Those are full blown IDEs. They come with all the extras. All the text editors that can become IDEs have extensions or plugins that enable what these other actual IDE do natively.
Nowadays using vscode to debug a running program is common, but that was something only restricted to full blown IDEs some years ago, I’d say that vscode is lightweight IDE that can be expanded, but vim is a text editor first and foremost. You can’t really debug code in vim AFAIK, the most you get is syntax highlighting, linting, automatic whitespace removal and auto formatting? Not sure about the last one.
IDEs are designed to support a software development workload. A text editor is designed to edit text files.