3 ms·
I am a home, amateur developer and I was always curious why developers would choose an editor instead of an IDE. When I started to code 25 years ago, there was
by BrandoElFollito 5y ago
I am a home, amateur developer and I was always curious why developers would choose an editor instead of an IDE.
When I started to code 25 years ago, there was no choice but as soon as I discovered IDEs I never looked back.
Startup speed may be an issue, but it is I believe insignificant for a coding session (of a few hours). Key bindings are portable. IDEs bring code completion, integrated debugging etc.
I am really curious.
- slezyr 5y ago1.) Speed. IDEs often take seconds to start and you just need to edit .md, .json, *.sh. 2.) Support of different file formats and ease to install a new one with Package Control. Often, it's just Ctrl-Shift-P -> Type "Inst" -> type format's name and it's done. 3.) Many IDEs show the typed symbols after some delay and I really hate it.
- BrandoElFollito 5y ago1 → this is true but as I mentioned, for a coding session it would not be an issue. I use vscode (an IDE) for these quick edits when my IDE of choice (jetbrains) takes quite some time to start. 2 → vscode is the same. Jetbrains has this problem, though (I raised that point with their support but this will not change, unfortunately) 3 → you mean that the text lags when typing? I never saw that but I work on reasonably fast computers and only use vscode and Jetbrains IDEs
- krimbus 5y agoMy opinion is that it depends on the work done (codebase, language, etc.). In the