News for hackers. Stuff that matters.

A comment on GitHub staff are required to use Teams by Sep 1, 2023. Parent comment

Re:GitHub staff are required to use Teams by Sep 1, 2023 by 0cf8612b2e1e on Monday February 13, 2023 @02:18PM (#34778743)
For chats, it is embarrassingly slow at rendering. Seemingly only maintains the last ~two dozen messages in memory, if you scroll back in history, you have to painfully wait for it to retrieve the text and then render it. Weird rendering bugs frequently.

Meanwhile, I remember reading full ebooks on my Pentium which were rendered as a single HTML file with zero lag.

[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by amaccuish on Monday February 13, 2023 @02:34PM (#34779033)
I have the same problem with Slack, unsure why Microsoft needed to copy the pitiful performance. That the Slack mobile apps mirror the non-existent reliability of the desktop clients is actually pretty amazing.
[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by dragonwriter on Monday February 13, 2023 @02:52PM (#34779309)
> For chats, it is embarrassingly slow at rendering

To be fair, despite all the other ways that Slack runs rings around Teams, rendering speed isn’t one of them.

But, yeah, you’d think this would be an easy opportunity for a big win for Teams.

[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by robertlagrant on Monday February 13, 2023 @03:19PM (#34779754)
Switching from Teams to Slack the first thing I noticed was the crazy good rendering speed of Slack. Teams you just lost your sense of where you were in your history it took so long. Slack slams it on the screen almost instantly.
[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by dragonwriter on Monday February 13, 2023 @04:24PM (#34780785)
> Switching from Teams to Slack the first thing I noticed was the crazy good rendering speed of Slack.

Huh, going the other way, I didn’t notice it get much worse; Slack seemed slow, and so did Teams, but not overwhelmingly slower. Might not have been “rendering” proper, could have been network topology of our orgs installations of each and more latency to Slack than Teams, or something like that.

[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by LeSaucy on Monday February 13, 2023 @03:39PM (#34780065)
Search is horrendous. There are strings that I am guaranteed to have written and it is unable to find them, nevermind the ui for it is absolutely unusable.
[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by VBprogrammer on Monday February 13, 2023 @03:59PM (#34780364)
Search is easily the worst. Video performance was pretty Terrible pre-covid but seems to have improved to the point of not usually a problem.
[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by ElectricalUnion on Monday February 13, 2023 @04:17PM (#34780673)
Going backwards in Teams is bad. Searching is a special case of going backwards and it sucks even worse.

It rolls back to the past, but lags, so it ends up showing you the wrong part of the history, rolling back to the present or a indeterminate past all while not showing what you searched for.

[ Parent | on HN ]
Re:GitHub staff are required to use Teams by Sep 1, 2023 by hulitu on Monday February 13, 2023 @04:05PM (#34780471)
Scrolling through history of a chat is masochistic. You get a web scrollbar and finding individual messages, even if you know where they are is a lottery.
[ Parent | on HN ]