Slack’s threads suck compared to Zulip’s. In Slack, threads only notify thread participants unless you choose to send it to the channel too, which defeats the purpose of threads by interrupting other conversations. In Zulip, everything in the channel/stream must be a thread, kinda like email.
Zulip does most things better than Slack. I can't stand Slack, it's slow, bloated, and the UX is bad. Zulip's UX is a breath of fresh air. It's just so quick to catch up on old messages, mute irrelevant threads, see everything in chronological order, zoom in or out... I just love it.
I've been using Zulip daily for over a month now and I love it! As do my colleagues who are now very happy users.
Looking forward to whenever Zulip implements /digress. That's something I realized was missing right from the start - how to "branch out" from a topic into a new one, creating some sort of sign/breadcrumb indicating that the message got a reply in a new topic.
Currently you can quote reply and change the topic for the new message, but there's no indication in the original topic that there was a digression, so discovery is a bit clunky.
I have no idea how Slack threads are intended to be used. Their own examples are very trivial and the implementation feels like like a first pass that they never did any usability testing with.
Slack threads seem designed to ensure you can't follow a conversation without branching off into numerous sidetracks, which are hard to find when you're directly addressed.
