Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub staff are required to use Teams by Sep 1, 2023

twitter.com

Post reply on HN
Print view View original

431–440 of 725 posts

Re: GitHub staff are required to use Teams by Sep 1, 2023

#431

Post by ElectricalUnion »

LeSaucy wrote: post #383
0cf8612b2e1e wrote: post #269

Earlier quoted context omitted.

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.

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.

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.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#432

Post by gcbirzan »

bsder wrote: post #378
MaKey wrote: post #245

Earlier quoted context omitted.

The Linux app doesn't even support screen sharing when you're using Wayland. I was forced to try out the browser based variant (meeting link opened the web variant instantly instead of giving me the choice to use the app instead) and can now finally share my screen (even single windows!). Also I can now use backgrounds, which the app didn't support.

> Wayland Don't blame Teams for the fact that Linux can't sort out its Desktop GUI situation.

Yes, the second graphical API that Linux supports in 30 years, definitely Linux's problem.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#433

Post by Infernal »

ChymeraXYZ wrote: post #411
wvenable wrote: post #249

Earlier quoted context omitted.

What does it mean to be worst-in-class for text chat or video conferencing. Video conferences look and sound great. Text chat is text chat. What am I missing here that's so awful?

> What does it mean to be worst-in-class for text chat I expect a chat program to show me all messages the have been sent in a chat, in so far the other party intends me to view them (have no been deleted etc.). That is not an expectation Teams manages to fulfill. I expect an edit (mine or someone elses) to be reflected on all my devices. That is not an expectation Teams manages to fulfill. I expect to do the same se…

I also expect to get notified of incoming messages - it was not infrequent that I would restart Teams and get 3-5 notifications of messages all at once, timestamped over the previous several hours.

As best I could tell, my client would simply lose connection to the server entirely silently. Normally I would find out when trying to send a message to someone, and noticing the delivery animation/indicator was not appearing. Restart Teams and boom, here's a little pile of messages I'd missed.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#434

Post by BazookaMusic »

bdlowery wrote: post #206
BazookaMusic wrote: post #145

One thing to keep in mind is that there's a security angle to this as well. It is beneficial for a company to centralize all of its communication through one service which can be audited for security and also support all the features required to meet the internal Requirements. Having multiple tools multiplies the work needed to maintain security standards. Of course, I'm not saying that teams is more secure than comp…

They aren’t centralizing their communication in teams. It’s being used for video conferencing. Everything else remains in slack. Read the image in the tweet, it’s only 100 words or so

It's unlikely that they won't use it for more eventually if this works. They're probably playing it safe by mentioning only video conferencing.

As an example, if meetings are made in teams and people comment during the meetings, their input will be in teams. Further communication around the meetings is likely to stay in teams. They're making it inconvenient to use slack or other means.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#435

Post by stonogo »

vladvasiliu wrote: post #361
kdtsh wrote: post #235

Earlier quoted context omitted.

Likewise, I don’t particularly like it but it’s fine. My biggest gripe is nonexistent official Linux support - I hate having to use a package maintained by one person on GitHub to get a desktop application for Linux, when this application is so critical for my day to day. But besides that it works fine.

What do you mean? MS puts out debs and rpms for teams: https://www.microsoft.com/en-us/microsoft-teams/download-app

Those were EOLed last year. Microsoft's current guidance is to use the PWA in Chrome or Edge.

https://office365itpros.com/2022/09/19/teams-pwa-linux-clien...

It's easy to miss, because it was only posted to the Office365 Message Center, and not announced anywhere else. Discussed here: https://news.ycombinator.com/item?id=32678839

Re: GitHub staff are required to use Teams by Sep 1, 2023

#436

Post by hulitu »

FooBarWidget wrote: post #376
jacquesm wrote: post #194

Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…

You think Teams is horrific? At a certain large company who's all-in on Google Cloud, they use Google Chat. Everbody wants to use Slack but management thinks it's too expensive while Google Chat is free and comes with G Suite which they already paid for. You don't know what horrific means until you've used Google Chat. Teams is a delight compared to that.

I hate to say it, but, my experience with Google chat was better. It was around 2016 so maybe they haven 't implemented web 3.0 stuff yet.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#437

Post by ElectricalUnion »

wintogreen74 wrote: post #266
dragonwriter wrote: post #238

Earlier quoted context omitted.

Teams is minimally usable, but its pretty much worst-in-class for…everything it does. It’s two compelling selling points seem to be (1) that “nobody every got fired for buying IBM” now applies to Microsoft more than IBM, and (2) moreover, users don’t actually buy Teams qua Teams, they get a Microsoft 365 subscriptions for some of the things where Microsoft has not-worst-in-class solutions, and Teams comes along for t…

>> but its pretty much worst-in-class for…everything it does It has good outlook calendar integration; joining from a single click in my calendar view is much nicer than having to open the occurrence & find the zoom link.

> It has good outlook calendar integration;

It has enforced outlook calendar integration; by default you create a Teams meeting whenever you create a meeting, choosing to implement the meeting in a competing product is annoying at best.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#438

Post by hulitu »

FpUser wrote: post #374
jacquesm wrote: post #194

Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…

>"I know they don't have a reputation for writing good software" I think they have a problem that regular person supposed to hate MS and Windows. I also think MS is quite capable of and does produce good software be it their own OS, Visual Studio, Visual Studio Code, Word, Excel, Flight Simulator etc. etc.

> I also think MS is quite capable of and does produce good software be it their own OS, Visual Studio, Visual Studio Code, Word, Excel, Flight Simulator etc. etc.

All i can say: good luck using it.

I did not have, any.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#439

Post by ElectricalUnion »

SV_BubbleTime wrote: post #386
smcleod wrote: post #355

Earlier quoted context omitted.

What on earth have you used before?! I struggle to think of anything worse than Teams, maybe Amazon chime but pretty much everything I've used over the years is a good step up from Teams.

We used Webex, LogMeIn, GoToMeeting, and Zoom. I have yet to have a major complaint about Teams. It works, I have my meeting and I close it. I don't know what some of you want in a video conferencing app.

> It works, I have my meeting and I close it.

I wish that was true. Good for you. Not good for people expected to be "online" in it for longer.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#440

Post by dragonwriter »

robertlagrant wrote: post #351
dragonwriter wrote: post #312

Earlier quoted context omitted.

> 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.

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.

> 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.

Post reply on HN