I mostly agree, that said, after VS Code starts, it runs pretty well. I almost didn't try it after Brackets and Atom as they were really slow. I haven't tried zed, so can't speak to it. VS Code was really just the first editor that I used with an integrated terminal and the directory tree. Just those two features made it a great fit for my workflow. I'm able to use the CLI to run/debug without leaving the editor, and/or run git commands from the terminal as well.
I mostly agree, that said, after VS Code starts, it runs pretty well. I almost didn't try it after Brackets and Atom as they were really slow. I haven't tried zed, so can't speak to it. VS Code was really just the first editor that I used with an integrated terminal and the directory tree. Just those two features made it a great fit for my workflow. I'm able to use the CLI to run/debug without leaving the editor, and/or run git commands from the terminal as well.
Because it runs a bunch of background processes in C++, Rust, and does text rendering via WebGL.
Programmer editors with such capabilities are decades old.
https://en.m.wikipedia.org/wiki/Brief_(text_editor)
I know they use a lot of background processes to get the performance, the point is it works pretty well.
As to the second, I'm unaware of a gui editor with a built in interactive terminal prior to VS Code.
1 reply →