Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Used to be some time ago when downloads were ~5-7mb. Nowadays it uses Electron:

/Applications/Slack.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework



sort by: page size:

My guess is Slack likes to keep pages around, and each workspace is a separate page that are individually pretty heavy. So if I'm logged into 4-5 workspaces that adds up quick.

Slack does not use the OS webview, it is Electron. I don't think it's a 3MB download - if it is it must just be an installer that installs the real thing? I haven't looked recently.


10+ electron apps seems excessive, what other Electron apps are you running? I think Slack is the only one I'm running (that I know of)

I don't like Slack for that reason, but it's a Slack issue, not Electron. Other Electron apps (vscode, keeweb for example) aren't that resource hungry.

Slack uses ~ 2 GB of Ram and ~ 10% CPU when idle. I used it for a short while but now I'm just leaving a Slack tab open in my browser. Its exactly the same functionality-wise.

Basically I'm fine with Electron apps but I have yet to find one that I need and can't be replaced by a browser tab.


Have you noticed Slack slow down/use too many resources as a result of being an Electron app? Honest question, I've never used Slack, but have used other Electron apps and never really have any issues.

Use Slack on the browser. Works great. No performance or resource usage issues.

Not sure why so many people use the desktop app. It's an Electron app so of course it will suck up everything.


My Slack app on MacOS has been up for awhile. Current usage is 197+183+132 = 512MB. Much better than before, but still not small.

The Slack client is a terrible memory hog in my experience. I can't believe they need to use Electron instead of the platform native FWs.

Slack took great pains to make the client not be a memory and CPU hog.

Still better than Teams though. (Which is also in Electron.)


The Slack app is Electron based and pretty bloated too in my experience. I want a native app.

I remember when Slack in a Chrome tab committed 3-4 GB. Sounds like they've made improvements.

Standalone client and its helpers are sitting on ~800MB committed on my install of High Sierra. Might be worth a shot.


Slack uses electron if I am not wrong.

To my knowledge, Slack has always been an electron app. Did they use something else initially that was unnoticed?

Slack uses Electron, doesn't it?

I'm not a massive slack (or electron) fan but with it open right now in 7 teams it's using around 85mb of memory. It's improved a fair bit.

Why is Slack still an Electron app? I stopped using it because it's so slow. Native apps are fast.

Slack is using 89mb here. I never notice it running, personally.

As an aside, I don't believe the Slack app is taking full advantage of ElectronJS. It's essentially still just a wrapped webapp. (They run the same version in the browser.)

Full ElectronJS apps can use something called ASAR which effectively creates a super efficient bundle for loading application code at launch. More here: https://github.com/atom/electron/blob/master/docs/tutorial/a...


Slack and the Jira suite are terrible.

Slack web downloads 40MB of Javascript. The macOS Slack client, that I guess should have all that stuff already, downloads 10MB of stuff just by starting it (and going directly to a private text only chat).

next

Legal | privacy