![]() ![]() Video games, linkedin, HR profile, email photo, etc. One of the people in my IT department, the photo on all of their accounts is a bath toy. You start at the beginning and just continue reading the page until you're at the end. In Teams, because everything flows in the same direction and within the same space everything is right in front of you and catching up after a few days away is like reading a newspaper.In large channels with hundreds of users, this makes catching up on conversations after a day or two off a giant headache. The weird mechanics and "unintuitiveness" lead to some people replying to a message within a thread, some people replying within the main channel, and some people doing both.In Teams, this concept doesn't even exist.Right next to the send button in the thread pane is a box to send your message to the main channel. The application actively wants you to make things more confusing.In Teams, threads are children directly under the parent message with formatting/boxes around the thread to make it clear what is attached to what.Which is a bit awkward and the only way to get rid of it is to hit the X in the top right corner, which is again a weird mechanic for a chat program. As you navigate through channels, the thread pane doesn't care it stays open to whatever thread you opened. The threads open as a stand alone pane that have no attachment to the channel/message they're under.In Teams, starting a thread requires hitting the reply link directly under the message, which is exactly where you focus will be when you're done reading a message and ready to reply.It's an unintuitive place to put it and weird mechanics to use it. Starting a thread requires hovering over a message and hitting a small button in the upper corner of a message. ![]() Teams wants their channels to function more like a Facebook timeline with top level "posts" and child comments. Slack wants their channels to function like an IRC channel and threading seems to be there because enough people asked for it. The real difference, in my opinion, is ideology of the developers. ![]() Threading is the one place where I think it is significantly better than Slack. Seems the same to me as Teams when I used Teams long ago.įirst let me say that I'm not a huge fan of Teams, there are a lot of things I don't like about how it works. I guess you don't visit the internet very often:Īnything specific about Slack threading that is bad? We use it all the time and I've never noticed any issues. I've never right-clicked on a picture in teams to see it. While I think threading is retarded and horrible, I have a few devs that are HELL BENT on using it and I do not share your opinion about threading in slack being poorly.īut maybe I haven't seen a good threading option (Teams does not have one either.) so that could be it. As far as I can tell, Slack just wants to be an IRC channel and has no interest in threading, so makes it as janky as possible to discourage its use. ![]()
0 Comments
Leave a Reply. |