Live data from Hacker News

Slack client for the terminal

github.com

11–20 of 184 posts

Re: Slack client for the terminal

#11
post #7
post #6

Earlier quoted context omitted.

Because the amount of users who don't care or notice performance or memory usage issues is immensely greater than the amount who cares.

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

#14
post #7
post #6

Earlier quoted context omitted.

Because the amount of users who don't care or notice performance or memory usage issues is immensely greater than the amount who cares.

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 a lot of hubris in assuming their position as a market leader is unassailable.

This is only your very free interpretation of the comment you responded to.

I personally only encounter slack in companies I freelance for - if it does not perform, I file a ticket with whoever does office supplies and demand a bigger computer.

Re: Slack client for the terminal

#15
post #7
post #6

Earlier quoted context omitted.

Because the amount of users who don't care or notice performance or memory usage issues is immensely greater than the amount who cares.

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.

Sure, but who buys into a messaging platform because the client makes more efficient use of resources? Don't get me wrong, it's on the list of priorities somewhere but the decision to go one platform over another will be made miles above.

Re: Slack client for the terminal

#16
post #12

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

> 1GB of RAM You meant 1MB, right? ;-)

It shouldn't take more than 1MB, but a "power user" with the stock Slack desktop client will probably see RAM usage of 1.5 GB[1]. So* GP was referencing the fact that currently the Slack desktop client is using >1GB and that is way too much.

* I recognize your sarcasm, but figured I'd reply anyway since the internet is a weird place and lots of people might not catch the joke.

[1] https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memor...

Re: Slack client for the terminal

#19
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.

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

Re: Slack client for the terminal

#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

Post reply on HN