Hacker News Reader

Comment by poorman | Hacker News Reader

I could really use this seeing as... https://twitter.com/NickPoorman/status/737647940026634240

I connect to Slack from my favourite IRC client (Irssi) after getting fed up with the memory that the official client used. It's not as retro-cool as this C64 port but it fits my command line orientated workflow better than the Electron app did and allows me to build my own client-side plugins in Perl.

Use 'Glass TTY VT220' font (at 20 point) in your terminal app and your retro-cool game will increase two levels.

I really am sick to death of applications built ontop of Electron Shell et al, what an utter waste.

Yep I put a ticket in for something simialr(grows to about 2GB every 2 days or so), and was told it's expected behaviour!!

Everyone says scrolling back through history is a feature, but it grinds to a halt before you can scroll back very far anyway.

Historic messages don't need to be cached in RAM if it's several pages above the proverbial fold.

However I'm not convinced it's just historic messages that's eating up the memeory. IRC clients aren't this bad even with thumbnail support like Slack. Whuchever way you look at Slack, it's needlessly wasteful.

And I thought that my 700MB was bad.

My slack hovers at only around 920 real mem and 1.6GB total.

Wow, you really need to be in less slack teams...

That's no excuse for 17GB of memory usage...

That memory footprint is inexcusable even if he were literally on one thousand Slack teams. Functionally, Slack is more or less a shiny wrapper on IRC, and you can run dozens of IRC channels in a few megabytes, if that.

Reply on news.ycombinator.com