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
Slack client for the terminal
31–40 of 184 posts
Re: Slack client for the terminal
#32Apps 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?
Re: Slack client for the terminal
#33Earlier 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.
Re: Slack client for the terminal
#34I 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!
Re: Slack client for the terminal
#35Yes 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
#36I 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?
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
#37So 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
Re: Slack client for the terminal
#38Earlier 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.
Re: Slack client for the terminal
#39I 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 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
#40What 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 ;).