4 ms·
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 C
by methyl 10y ago
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.
- runn1ng 10y ago> writing Chrome app Note that Google will stop supporting Chrome Apps in 1 year or so. http://blog.chromium.org/2016/08/from-chrome-apps-to-web.html http://blog.chromium.org/2016/08/from-chrome-apps-to-web.htm...
- methyl 10y agoThis is too bad :(
- lawnchair_larry 10y agoWriting a chrome app to save you from chrome's bloat seems like a dead end. Just write a native client, or at least java/c#.
- methyl 10y agoIt'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.
- lawnchair_larry 10y agoSlack 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.