I know it's a defacto complaint to leverage against Electron apps, but memory usage notwithstanding, I've never run into much lag issue on any major Electron app.

▲

arcfour 10 hours ago | parent | next [-]

Surely there is a more effective way to write an app than to bundle an entire end-of-life browser and Node.js runtime into a 600MB monstrosity.

▲

paxys 9 hours ago | parent | next [-]

Electron apps don't have to be 600 MB. VS Code is an entire fully-featured IDE and is a 90 MB download.

▲

shawn-butler 8 hours ago | parent [-]

VS Code package in my applications folder is 600+ MB.

The Electron Framework.framework it contains is 400+ MB alone. I don't understand where you come up with your 90 MB figure?

▲

ethmarks 8 hours ago | parent [-]

The VSCodeUserSetup file from https://code.visualstudio.com/download is in the 90MB range.

Perhaps this file is just the installer and the actual system files are much larger? Or maybe your 400MB figure comes from a bloated install? Just speculating here.

	▲	piperswe 6 hours ago \| parent [-]
		Presumably the setup file is compressed, and the installation on disk isn't

▲

hluska 10 hours ago | parent | prev [-]

Of course there is, but not every decision in computing is (or should be) about raw efficiency.

▲

ToucanLoucan 10 hours ago | parent | prev [-]

It depends. Numerous times when internet is spotty Slack and Discord both on different occasions have brought my systems to a halt until they can complete whatever task is stuck waiting (or I force close them).

It's really fucking obnoxious that somehow a goddamn web app in a wrapper is managing to cause system wide hangs.

▲

Vilian 10 hours ago | parent | next [-]

True, i'm gonna start limiting electron apps CPU and IO percentage to not halt everything

	▲	nsriv 10 hours ago \| parent [-]
		I think that's probably a recipe to hit the limits more often and end up being more frustrating, depending on your hardware.

▲

1718627440 7 hours ago | parent | prev [-]

Can't you interrupt them (aka SIGSTOP) instead? Then you could resume them, instead of reopening them and potentially using state.