To be fair, you can turn most text editors into IDEs, independent on our technologies, a lot of the time we do just that.
I know that vs code is more like an IDE for me these days because I have different configurations for different technology stacks and they make the development experience much different than it would be without 100 or so plugins.
I kind of agree with that. Even though most code-/text editors are meant to simply write some lines of code, they can be extended with tons of extensions, modules, plugins, etc., why you might end up with something close to an integrated development environment.
True, but would you please care to explain the difference, since it seems to differ based on person as well as when a certain definition made its way "into the wild"?
Back in the day (early 90s) an IDE was something that came with the language. Eg, you install the compiler/interpreter and that came alongside an editor that allowed you syntax highlight, debugger and to execute the program.
See Turbo Pascal, Delphi as well as nowadays Android Studio or Visual Studio.
To that definition, I'm not sure which "IDE"s fit the bill. VSCode might, depending on language but in a reverse way (eg: the Go plugin can install the language as well as required tooling and leads VSCode to provide all the above functionality)
The last time I used an IDE, it was effectively just a driver for the editor/compiler/linker/lsp/etc components - most of which are or can be separate tools.
My terminal can drive all those parts. As you didn't put forth a specific definition of an IDE, can I call my terminal an IDE (the most language agnostic, plugin friendly, open IDE ('ve ever used)? 😉
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.
Code editor != IDE 😉
Damn, I'm still thinking
You are right. Sublime, Atom and Visual Studio Code are Code Editors. Not IDE’s
😉
To be fair, you can turn most text editors into IDEs, independent on our technologies, a lot of the time we do just that.
I know that vs code is more like an IDE for me these days because I have different configurations for different technology stacks and they make the development experience much different than it would be without 100 or so plugins.
I kind of agree with that. Even though most code-/text editors are meant to simply write some lines of code, they can be extended with tons of extensions, modules, plugins, etc., why you might end up with something close to an integrated development environment.
True, but would you please care to explain the difference, since it seems to differ based on person as well as when a certain definition made its way "into the wild"?
Back in the day (early 90s) an IDE was something that came with the language. Eg, you install the compiler/interpreter and that came alongside an editor that allowed you syntax highlight, debugger and to execute the program.
See Turbo Pascal, Delphi as well as nowadays Android Studio or Visual Studio.
To that definition, I'm not sure which "IDE"s fit the bill. VSCode might, depending on language but in a reverse way (eg: the Go plugin can install the language as well as required tooling and leads VSCode to provide all the above functionality)
The last time I used an IDE, it was effectively just a driver for the editor/compiler/linker/lsp/etc components - most of which are or can be separate tools.
My terminal can drive all those parts. As you didn't put forth a specific definition of an IDE, can I call my terminal an IDE (the most language agnostic, plugin friendly, open IDE ('ve ever used)? 😉