2 ms·

An IDE is integrated: it comes with the tools (debugger, build system, language support, etc) built in. If they're not integrated, it's not an Integrated Develo

An IDE is integrated: it comes with the tools (debugger, build system, language support, etc) built in. If they're not integrated, it's not an Integrated Development Environment. I'd say things like VS Code, Sublime Text, Vim, and other plugin-based editors are "Plugin-based development environments", or PDEs (my term). Most IDEs these days are hybrids; they come with an integrated environment and support plugins as well.

euos 3y ago
Things like Eclipse IDE, IntelliJ and such are packages and not the products. Think distinction between Linux distro and Linux kernel. E.g. my former team used to ship "IDE" - that is, use new project wizard to setup your folder, use editor to write the code, press a button to build, debug and profile. We also shipped standalone "visual profiler" - that had custom configuration for window layout/toolbars and stripped down list of included plugins. You open an executable, profile it, see per-line metrics in the read-only editor (that was a complete editor from the IDE, just in read-only mode). So, does dropping a bunch of plugins (that noremally should not activate unless used) suddenly convert sluggish IDE into fast editor. I feel like the negative perception of IDEs usually comes from busy UI. Devteam needs to balance discoverability (e.g. adding UI for configuring build and debug) and perceptions of the lightweightness.