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

351–360 of 725 posts

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

#351

Post by robertlagrant »

dragonwriter wrote: post #312
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.

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

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

#352

Post by boring_twenties »

jacquesm wrote: post #268
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?

For me the ability to seamlessly start a meeting, pull in 10 participants from different organizations by just sharing a URL and be off to the races a few minutes later is what makes the difference. If I have to spend even a couple of minutes debugging audio/video issues, dealing with people that can't seem to join, people that are trying to install a client that they then can't get to work, people that need to make…

> the ability to seamlessly start a meeting

Must be nice. For me it simply refuses to start or join any meeting, gives a useless error message about trying again later.

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

#353

Post by jrochkind1 »

X-Istence wrote: post #327
jrochkind1 wrote: post #231

Earlier quoted context omitted.

> Sharing a single window makes Teams minimize the window with everyones video camera on it into a small window in the corner of your primary screen. I have a 49" wide screen, I can have that Teams window open (so I can see faces/people) and share a window at full-size for everyone else, STOP minimizing that window. Took me a while to figure this out, but, and if I understand what's going on and you didn't realize it…

> Try clicking on that tiny window with everyone's video feed on it. It gets bigger again into a full (and resizable) window with everyone's video feed, while the window you are sharing is still being shared (and outlined in red). Yup, until you click away from that window, suddenly its the little window in the corner again and it is no longer available in Mission Control, well the little tiny window is. So I end up…

I don't use mission control, but I'm able to have the bigger window stay open while I click in the window I'm sharing, and also click in other unrelated windows I'm not sharing.

Not sure why it's different for me and you, but I'm not shocked, the software is definitely a mess.

But I somehow don't have the particular problem you are having... anymore.

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

#355

Post by smcleod »

kenjackson wrote: post #320
wvenable wrote: post #218

Earlier quoted context omitted.

It's so weird -- I use Teams all the time and I've never had a serious problem with it. It's not the greatest software ever made but it's certainly functional. It's definitely getting a lot of work done to it.

We also use it every day. That said, I feel like I know a lot of devs who think there are a lot of things that are unusable (or the equivalent). Everything from Visual Studio to the display on their iPhone to modern cinema and science fiction in general to In-and-Out burgers. As a general rule, I discount their take on pretty much anything. Is Teams great? No. Its better than what I used before it though, and its pro…

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.

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

#357

Post by mrweasel »

meitros wrote: post #4

"for the sole purpose of video conferencing". They're still using slack for day-to-day...

Yeah, that was interesting. I wonder if Teams have acquired the feature that Google Meet have to extremely simply setup a meeting and just do it all in the browser. The quality of the video and audio is fine in Teams, it's all the surrounding stuff that's wonky.

So it they can easily create a meeting without using the Teams client, then it might be just fine.

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

#358

Post by paxys »

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…

> it is incomprehensible that Microsoft would ship something so utterly broken

Is it though? Heck Microsoft shipping a high quality product is the exception. The entire company runs on half-assed software being pushed by sales teams to CIOs and others high up on the corporate ladder who evaluate it on the basis of dollar amounts, kickbacks and marking checkboxes and not factors like usability and user experience.

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

#359

Post by [deleted] »

X-Istence wrote: post #327
jrochkind1 wrote: post #231

Earlier quoted context omitted.

> Sharing a single window makes Teams minimize the window with everyones video camera on it into a small window in the corner of your primary screen. I have a 49" wide screen, I can have that Teams window open (so I can see faces/people) and share a window at full-size for everyone else, STOP minimizing that window. Took me a while to figure this out, but, and if I understand what's going on and you didn't realize it…

> Try clicking on that tiny window with everyone's video feed on it. It gets bigger again into a full (and resizable) window with everyone's video feed, while the window you are sharing is still being shared (and outlined in red). Yup, until you click away from that window, suddenly its the little window in the corner again and it is no longer available in Mission Control, well the little tiny window is. So I end up…

[deleted]

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

#360

Post by moonchrome »

matwood wrote: post #281
moonchrome wrote: post #177

Earlier quoted context omitted.

>Making Teams not suck doesn't move their revenue dial one iota. That's not true, I would switch to Office 365 if it didn't suck. Having an entire suite fully integrated and under one license is a great value proposition - but the thing has to work. I've had to use Teams over the years and every time I get the same shitty experience I've had with it 5 years ago when I first tried it.

> I would switch to Office 365 if it didn't suck. From what? O365 collaboration is terrible. If you do joint document editing, O365 will drive you nuts after using something GSuite. What many do is have GSuite and then O365 for people who need office products for various reasons.

That's my point - I would replace GSuite and Slack for O365 if the later wasn't so bad. I have the office 2019 package when I need to use office apps.
Post reply on HN