It's VERY memory heavy. When I open 4 channels it could eat as much as 4GB, comparing to 300MB per card when it's open in Chrome. That's why I started writing Chrome App which will simulate native Slack client and be much more memory efficient.
It's not chrome's bloat, it's Slack that's for some reason broken. I don't have such problems with VSCode for example. Also it's reusing already opened Chrome instance which should make memory usage more optimized.
Slack might be making it worse, but come on. Chrome is huge. Check out the memory and cpu usage of VS Code, and compare that to any other text editor. An instance of chrome just for text editing blows my mind.
