171–180 of 243 posts
Earlier quoted context omitted.
They actually just fixed that in 4.0: https://slackhq.com/introducing-a-more-efficient-slack-deskt... I'm currently sitting at 400MB total usage (including helpers) for 4 workspaces.
400MB? Not bad for a chat client that sends a few bytes of text.
If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.
If you start using it using the Cloud solution, can you then later easily migrate to the On-Premise version?
(I work on Zulip.)
If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.
Earlier quoted context omitted.
Has anyone tried Twist ( https://twist.com/ )? It looks a lot like Zulip but with a nicer UI. I think it is crazy that Slack has not invested more in first-class threaded, context-aware conversations.
Tried it. While the interface looks 'nicer' at first glance, it fits far less content on the screen. It also had more of an email-y vibe while Zulip has more a chat-y vibe, which I personally prefer. Beyond that, Zulip is open source and self-hostable, while Twist is not. Side note, we have a chat about self-hosting set up on Zulip at https://homelabos.zulipchat.com/ with 85 members and growing. It's been great for n…
Earlier quoted context omitted.
Wish we wouldn’t use such language, “sucks less” is highly subjective and your opinion but we don’t need to disparage Slack in order to make a point that alternatives like Zulip are available. Seems like especially poor tone on an outage thread... “Don’t kick them while they’re down” or something?
2GB of RAM use for 6 open tabs in Slack is pretty awful, their desktop client has set the bar to compete with Slack on performance very low. This abusive resource usage has created a dislike of Slack among a subset of its users.
I really don't like the heavy dependence on Slack that my (and a lot of other) company has. The outage is frustrating.
See, I love it. I work for a mostly-remote company and before Slack we had an IM product but it was a 1:1 chat. Having an always-on chat room for the entire team, knowing other teams use the same product and I can pop into their chat room, spinning up channels for project teams, etc. It's been a huge boost to our company. And since so many companies have settled on the same solution, when I'm working with a client I…
Earlier quoted context omitted.
I don't mean it in a disparaging way. Most software sucks to some degree so the goal is to find something that "sucks less". Pretty much everything can always be improved on.
"more pleasant to use and less buggy." Borrowing from Lin Manuel-Miranda's Thomas Jefferson: > These are wise words, enterprising men quote 'em > Don't act surprised, you guys, 'anaphor wrote 'em It's a nicer way to convey the same idea, without triggering a combative emotional response in reaaders.
Earlier quoted context omitted.
But... we pay managed solutions like Slack so we have 100% uptime...
We don't pay for 100% uptime. We pay so that we don't have to put the time into operating a service. That way we have more of our time to focus on our business problems.
Earlier quoted context omitted.
You can apply the same logic to email and the internet in general.
No, Slack is more like sunlight, which also exhibits a single point of failure for most orgs. While the sun does go down, it somehow seems more reliable.
Yep. It's pleasant at first and a genuinely useful tool when used correctly, but if you're not judicious with your usage, you could get burned.