| I agree wth this comment a lot. I work at Stack Overflow, where our company chat is split between Slack and an internal chat product we made ourselves years ago. I think the "comments as threads" concept helps solve some specific use cases (like room clutter) but not the use cases I personally care about the most. The "in-line method" mentioned in this other article about the change is my preferred method: https://www.fastcompany.com/3067246/innovation-agents/the-un... My gripe doesn't stem from rooms being too cluttered, it stems from if there are 4 people talking at once and I'm in two different conversations chains with them, I'd like to explicitly reply to a specific message and carry on the convo. not hide it in a comment thread. On our homebuilt chat product this is the difference between starting a message with `@Name` or hitting "reply" on a specific message and having `@:{Message Id}` as the beginning of your message. It shows the same to the users, they seen `@Name`, but if it's a specific message reply when they hover over the message the one it's in response to gets highlighted (and there's a button to scroll to it if it's off-screen). I think this Slack feature, like most features, is targeted at helping people using chat sitting in the same room or office together. I work at a very remote company where with some people I share less than 2 hours of a work day. I want better chat tools centered around making our async communication flow better. Not out-of-room comment threads. |
Try Zulip, actually. We use it and it does that exact thing very well.