5 ms·
I use VSCode (electron based) on a flight cross country regularly. I generally have enough power for the flight (4-5 hours), without much problem. The memory u
by bluejekyll 8y ago
I use VSCode (electron based) on a flight cross country regularly. I generally have enough power for the flight (4-5 hours), without much problem.
The memory usage hasn’t been bad enough for me to notice it stealing resources from other apps that need it. I don’t think most users notice.
I’m not talking about you. It’s clear this is a big deal to you, and so I assume you don’t use any electron apps. I think that’s a gamble most companies would make, losing a small number of users, to have the potential to gain many more.
- scarface74 8y agoVisual Studio Code = real work with a complicated set of features. I expect it to consume a fair amount of memory and battery life. Slack - Shouldn’t.
- maltalex 8y agoWhat makes VSCode more “real” in your opinion?
- icholy 8y agoExample https://code.visualstudio.com/blogs/2018/03/23/text-buffer-reimplementation https://code.visualstudio.com/blogs/2018/03/23/text-buffer-r...
- kylel 8y agoI think with Slack, the computational workload is just network I/O and rendering text and images. With VS Code, in addition to rendering text, there is code linting and compilation, which is more intensive.
- mi100hael 8y agoI'm pretty sure VSCode is actually React-Native, not Electron. So there isn't the overhead of a full Chrome instance like there is for Slack or Atom.
- acemarke 8y agoI'm a React fanboy, but no. VS Code is definitely written on top of Electron, and as far as I know the codebase is entirely custom rather than using any kind of JS SPA framework.
- GordonS 8y agoVSCode is like the poster child for Electron, Electron done right. I often bring up VSCode when people are hating on Electron here. Yes, it's easy to make crappy memory hogs with Electron, but it's also possible to make fully-featured, snappy, great applications. Such as VSCode.