Live data from Hacker News

Slack client for the terminal

github.com

31–40 of 184 posts

Re: Slack client for the terminal

#31

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

You can actually connect to Slack via IRC: https://get.slack.help/hc/en-us/articles/201727913-Connect-t...

Re: Slack client for the terminal

#32
post #5

Apps like Slack make millions of dollars every day. What's their excuse to not hire platform-oriented devs to build native apps that run smoother?

It was always a website in nice packaging. Actually I don't want slack engineers to build a semi web browser, it's already crappy enough with the good foundations. A rebuild only increases one thing: bugs. Although Slack runs slow and GIFs in background are like CPU stress tests it does not have major bugs in functionality. Never touch a running system... it's easy to rebuild a simple chatroom experience but Slack is far from simple... it has a vast amount of features on closer look.

Re: Slack client for the terminal

#33

Earlier quoted context omitted.

There's also a fair amount of hubris in assuming that assuming that you know the market better than the market leader. They're killing it for a reason, and it just may be that the market they're targeting cares more about the app Just Working than about the RAM consumption.

The status quo justifies the status quo, said every market leader ever.

A valid point. I don't know why it was downvoted since it counterpoints the argument he was responding to.

Re: Slack client for the terminal

#34

I just want something between this and Slack's mac app, which sometimes doesn't want to load on even Starbucks wifi. Ideally a GUI app that can load messages on airplane wifi would be amazing. Every time I try to open slack on an airplane it just sits there loading and loading and loading. Maybe one day!

Oh man, that "you can't even see the messages that were in RAM when your computer went to sleep because we're doing... something... with your slow network" behavior is infuriating. I work a lot on airplanes and mobile hotspots, and it comes up depressingly often.

Re: Slack client for the terminal

#35
I remember there was a multi-IM client called centericq which was console-based and pretty awesome. I used it for several years back when ICQ was still a thing.

Yes I know about irssi and friends, but they're not really having an UI, many things are commands or config based, but centericq was.

Re: Slack client for the terminal

#36
post #25

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

I was gonna say there's no way slack uses that much, then I actually looked. 750+mb.... What in the world are they doing?

> What in the world are they doing?

Literally no one knows! It's layers upon layers of code. Most of the layers can't even be understood by a single person, let alone the whole program.

Re: Slack client for the terminal

#37

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

Oh c'mon. Slack absolutely destroys IRC in terms of usability. And that's what ends up counting in the end.

Re: Slack client for the terminal

#38
post #7

Earlier quoted context omitted.

IMO that's a poor excuse, and leaves open a lot of room for competition. There's a lot of hubris in assuming their position as a market leader is unassailable.

There's also a fair amount of hubris in assuming that assuming that you know the market better than the market leader. They're killing it for a reason, and it just may be that the market they're targeting cares more about the app Just Working than about the RAM consumption.

Slack is merely the latest contender in a very long succession of group chat technologies. They will be usurped one day, but they are substantially accelerating their demise by making their product so infuriatingly slow.

Re: Slack client for the terminal

#39

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 even 2gb of memory?

Re: Slack client for the terminal

#40
post #4

What does the current emoji support look like? ( https://github.com/erroneousboat/slack-term/blob/b871a9ad0c8... seems to suggest they aren't rendered?) In my experience custom emojis is the most important driver of Slack use ;).

I have emojis turned off. Great feature.
Post reply on HN