[herbst]

It's been a while when I've used VS code in production but on Linux the issues with Atom have been less from the very start and VS Code simply never delivered the performance increase everyone was talking about. Maybe because I never made it an IDE but used it as editor.

On Linux Atom simply was the "better" choice for a long time.

[ryukoposting]

Having used Atom and VS Code on an old laptop in college, VS Code definitely does a better job when you throw it a large file, a first-gen i5, and 4GB of RAM. Likewise, at my first internship, I tried sublime on my work computer, which they had clearly just grabbed from the storage room (Windows 7! In 2018!). Sublime exploded into a million pieces.

My point is this: if we're being honest, all Electron-based editors suck. They're slow, and community-provided extensions are buggy and they integrate awkwardly with each other. But in my world (embedded firmware) there simply isn't a less-terrible option. VS Code is the least-terrible among them.

[herbst]

I honestly don't get that use case, I don't open large files in a text editor usually. But I agree that atom sucks in that degree.

Maybe slow never was the problem is kinda what my point is. In the end it's just an editor for text.

[ryukoposting]

I like to reverse-engineer web APIs (working on the NBA's stats API right now) and sometimes I have to open/autoformat JSON files with 500k+ lines.

As a firmware engineer, it's also frequently useful to be able to do hexdumps of large binary files in VS Code.