Hacker News Reader

Comment by StavrosK | Hacker News Reader

This ignores the fact that defaults matter, and defaults shape the usage of the tool. I want to reply in threats, but often don't, because it requires me to let go of my keyboard and fumble around with the mouse to do it. That's why I vastly prefer Zulip (which additionally isn't slow as molasses).

View on HN

I want to reply in threats

Look, I feel ya, but it is important to stay professional even in the face of annoying coworkers.

Nice fingers you typed that comment with, it'd be a shame if anything were to... happen to them.

Threads are an extremely important asset in large channels to maintain organization. Less important in ad-hoc quick conversations in small DM groups for sure. I've never experienced any issues with people not using threads and the UX around it has always seemed fairly smooth to me.

My issue is that I'll reply out of thread because it's much, much faster in Slack, and then I'll be kicking myself because that means I won't get notified of further replies (and neither will anyone else).

I'm always not sure when a conversation will need a thread. Sometimes I start a thread and then it's over with just one message that provides the answer. Other times I don't start one right away, but now if I start one then the first 4 messages of context will be missing at the top. I would use threads ofif there were a way to create them retroactively.

Another plus one for Zulip, huge improvement over Slack for me.

The reason I don't like threads is that I can't expand a thread without seeing it in the sidebar. That's so effing annoying.

Yeah, they really botched the implementation of such an essential feature.

Reply on news.ycombinator.com