Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack client for the terminal

github.com

Post reply on HN
Print view View original

71–80 of 184 posts

Re: Slack client for the terminal

#71

Post by guessmyname »

antjanus wrote: post #39
NikolaeVarius wrote: post #9

I use this personally. Its great. Hides all the cruft that people post in slack as text. I've been working on trying to extend it on the side. A chat client should not be taking over 1GB of RAM

how is it taking up that much data? I'm at 550mbs with 6 very active teams and while on voice chat. Dropped out of voice chat I'm at 340mb. Each team has 10-20 channels. I also use Discord which uses Electron and with it, I'm on 8 separate active servers with anywhere from 10-30 channels. This sits at 115mb without an issue. Can you tell me where these electron metrics come from where people have slack take up 1gb or…

> I'm at 550mbs with 6 very active teams and while on voice chat. Dropped out of voice chat I'm at 340mb

That's still a lot of RAM for a chat with giant emojis.

You have to consider that people reporting these issues with memory consumption are running the app in different operating system than yours. Maybe your system is optimized. I just checked my co-workers computer and his main Slack process is at +97MB but there are 3 instances of "Slack Helper" at +433MB, +297MB and +255MB respectively. That's over 1GB in total. So either you are just looking at the main Slack process (which at +340MB makes sense) or your Slack is leaking memory somewhere that your RAM monitor is not able to map.

Re: Slack client for the terminal

#72

Post by pjmlp »

drb91 wrote: post #51
Karunamon wrote: post #48

Earlier quoted context omitted.

Your failure to set your coworker's expectations for your availability or the failures of organizational culture being projected onto the messaging tool are not the fault of the messaging tool.

This ignores the fact that if you don’t respond to people contacting you you’ll get fired. As a salary you have no voice. The market simply optimizes for whatever is easiest for a ceo to install and maintain.

In countries that have actual work laws that wouldn't happen so easily.

Re: Slack client for the terminal

#73

Post by Karunamon »

gsich wrote: post #59
Karunamon wrote: post #53

Earlier quoted context omitted.

How is this Slack's fault, again? Or is the argument that messaging systems should be hard to install so they aren't misused? Seriously, what even is this comment chain getting at? If you work somewhere where always-on is a hard requirement, it doesn't matter what messaging system is used. Any place that would fire you for muting notifications would just as easily fire you for turning off email notifications. In shor…

Probably because Slack makes it easier to establish an "always-on" culture.

Literally any other instant messaging program would have the same effect if the culture is toxic enough to allow it.

Slack is no different other than name recognition and size.

Re: Slack client for the terminal

#74

Post by Karunamon »

tachyoff wrote: post #67
Karunamon wrote: post #48

Earlier quoted context omitted.

Your failure to set your coworker's expectations for your availability or the failures of organizational culture being projected onto the messaging tool are not the fault of the messaging tool.

Not only do we shape our tools, but our tools also absolutely shape us.

Your corporate culture shapes use of the tool a lot more than the design of the tool, especially when that tool's essential components are identical across the entire set of competitors.

Slack doesn't have some voodoo set of features that make it more problematic than Hipchat or Teams or Stride or Mattermost or (nn programs elided).

If your org sucks, your communication within that org will suck too. Let's not burn down the concept of instant messaging in the name of sucky orgs.

Re: Slack client for the terminal

#75

Post by solarkraft »

lozenge wrote: post #43
antjanus wrote: post #39

Earlier quoted context omitted.

how is it taking up that much data? I'm at 550mbs with 6 very active teams and while on voice chat. Dropped out of voice chat I'm at 340mb. Each team has 10-20 channels. I also use Discord which uses Electron and with it, I'm on 8 separate active servers with anywhere from 10-30 channels. This sits at 115mb without an issue. Can you tell me where these electron metrics come from where people have slack take up 1gb or…

Every Slack workspace creates an Electron instance. If you're on three workspaces, that's like running three totally separate browsers.

What the hell?

Re: Slack client for the terminal

#76

Post by sitkack »

antjanus wrote: post #39
NikolaeVarius wrote: post #9

I use this personally. Its great. Hides all the cruft that people post in slack as text. I've been working on trying to extend it on the side. A chat client should not be taking over 1GB of RAM

how is it taking up that much data? I'm at 550mbs with 6 very active teams and while on voice chat. Dropped out of voice chat I'm at 340mb. Each team has 10-20 channels. I also use Discord which uses Electron and with it, I'm on 8 separate active servers with anywhere from 10-30 channels. This sits at 115mb without an issue. Can you tell me where these electron metrics come from where people have slack take up 1gb or…

Back when I used Slack, I was on 8? different slack(s)? And my memory usage was around 1.5-2GB on OSX.

Re: Slack client for the terminal

#77

Post by guessmyname »

dewey wrote: post #2

Fun project but if you are just looking for a less crappy experience than their default client you could just use irssi and the Slack IRC gateway?

Not if your employer disabled the IRC Gateway, like in my case.

This terminal client seems to be using Slack's public web API.

Re: Slack client for the terminal

#78

Post by wmeredith »

Barrin92 wrote: post #20

So we've gone from IRC which worked perfectly fine to a billion dollar business just to port that software back to the terminal, where we started out to begin with I don't understand this world any more

Teach my CEO, Design Director, and EVP of Sales to use this terminal slack client and you’ll understand.

Re: Slack client for the terminal

#79

Post by kqr »

zitterbewegung wrote: post #63
brandonmenc wrote: post #27

Earlier quoted context omitted.

Well then everyone should feel stupid for not realizing you could make a billion dollars creating a sane sign-up and account management system for IRC.

Also , infinite scroll back , a standard set of easy to use clients, hosted services and API integrations.

I fail to see how those things should be part of the protocol. That's like complaining HTTP doesn't support tags for your bookmarks. It's so out of scope.

Unless, of course, you are talking about a user-friendly service offering IRC access to those who do not want to set up their own clients.

So, something like IRCCloud, which does exist, fyi.

Re: Slack client for the terminal

#80

Post by notjustanymike »

mping wrote: post #65

Obviously slack got something right, otherwise people would still use irc. It always amazes me how we devs fail to ack the business side of a success case as slack. And if any contender in the space fail to identify what slack got right they won't thrive. Maybe it was the ui, or some particular features, but they did resonate with the users. And now they are the benchmark that all the others will compare to.

My wife uses Slack. My 68 year old parents use Slack. They have no idea what IRC even is. Slack made an accessible IRC.
Post reply on HN