[arghwhat]

> Chromium's rendering engine is faster than most native cross platform toolkits.

Which toolkits are you referring to, and do you truly just mean the renderer, or the entire engine?

Chromiums renderer is pretty fast. Not as fast as direct rendering like Sublime Text does, but for very complex scenes, it will beat Gtk and Qt.

However, it's expensive to build scenegraphs for it (needed on every change), and partial updates are far more expensive than they need to be.

The end result is that, for something like an editor, Gtk and Qt will beat Chromium for responsiveness by a large margin, despite having much less performant renderers for the time being.

(You can get around some of these costs by using WebGL of course, but if you're doing manual rendering you have already thrown most of the reason for Electron out of the window, so why not do it natively where it will be even faster?)

> The memory consumption doesn't bother me either or come anywhere close to bottlenecking me, because I'm a professional using professional hardware.

This is an awful argument. That I have beefy workstation machines doesn't really matter when I'm usually mobile on a low-power laptop.

The difference between using VSCode and sublime/vim is several hours of battery life, and the difference between a comfortable lap and a warm lap.

This idiocy of "it's fine, there's enough resources" is why my colleagues expensive MacBook Pro's are hyperventilating 24/7, and it's a problem for poorer individuals that might not afford a powerful machine.

> Sublime is also pretty featureless compared to VSCode as well.

Matter of taste.

Sublime Text still has a very long list of plugins, and certainly does everything I will ever need an editor to do. I see no reason to pay the penalty of Electron to get support for NyanCat cursor plugins.

VSCode is also pretty featureless if you compare it to vim, and if we pull Emacs into the discussion, VSCode ends up looking more like nano/Notepad.

[qppo]

Its too early in the morning for me to get into a flamewar about this.

So all I'll say is that I get a lot of value out of VS Code as a tool, and I don't think it's slow. I think every point you bring up comes from a lack of experience and knowledge of the tool/platform, and it's not worth arguing about online.

[arghwhat]

I'm not saying that VS Code is not valuable as a tool - that would be a stupid thing to argue over.

I used VS Code for about a year, and occasionally revisit to reevaluate. Hell, I even gave Atom a (rather unwarranted) fair shot.

What I am evaluating is just performance and resource consumption, which is much worse than it needs to be due to the design choice of using Electron, which has little to nothing to do with the functionality it provides.

For me, the performance makes it uncomfortable to use. Others less fortunate will be experiencing something much worse than I am.

[toastercat]

I agree that VSCode is not "slow," at least not when you get used to it and definitely not in comparison to other Electron apps. I used Sublime Text 3 for a long time before Atom became popular. Immediately, I noticed that Atom was nowhere near as snappy as ST3, and was constantly hanging even on opening large folder structures.

VSCode was a breath of fresh air compared to Atom and the extension support was even more impressive. But very recently when I found out about the Sublime LSP package, I decided to give Sublime another look. The snappiness difference between ST3 and VSCode is night and day. Even though by no means does VSCode feels "slow" for my day-to-day work, the small speed improvements of using ST3 compounds to make for a greater experience overall to me.

[higerordermap]

I can add that extra heat from laptop on your lap running electron may cause fertility problems.