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

321–330 of 725 posts

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

#321

Post by casenmgreen »

polyvisual wrote: post #311
ukoki wrote: post #279

Earlier quoted context omitted.

You forgot the worst one! When you copy a message in Teams, it "helpfully" adds a header so you end up pasting "[Tuesday 12:54] John Doe" into random form fields / your terminal / your browser location bar ten times a day

My lord, that behaviour drives me mad. The experience of using the editor for writing and editing is horrendous.

Oh Gods yes - this.

I stopped editing text in Teams. I wrote text in an editor outside of Teams, then pasted it into Teams.

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

#322

Post by vinceguidry »

wvenable wrote: post #242
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.

I use Teams in Chrome a lot. Given that it's an electron app, I'm not sure it matters that much that it's "native" vs. "web app".

you do get the benefit of the app author's knowledge of how to tweak the chromium env to run it reasonably well. And of course the community support.

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

#324

Post by wvenable »

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…

I've never had a problem sharing a URL to get outside people in a meeting with Teams and, of course, it works in the browser. Are you sure this is still a problem?

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

#325

Post by [deleted] »

btilly wrote: post #243
samiru wrote: post #196

Earlier quoted context omitted.

I wonder if those who complain about Teams actually use it. They might not. My company forces us to use Google Chat. I would take Teams any day.

On what basis do you insinuate that other people's dislike is based on ignorance? That's a shallow dismissal of the kind that https://news.ycombinator.com/newsguidelines.html asks us not to do. Most of the time people's dislike is based on past bad experiences. If you think that those experiences may be out of date, indicate what has improved. If you like one product better than another, say why. Personally I have 25…

[deleted]

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

#326

Post by symfoniq »

FinalBriefing wrote: post #307
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.

On a Mac, I got stuck in some sort of loop that prevented me from joining any calls, and even uninstalling the Teams app didn’t fix it. I had to use my iPhone for every Teams call, and sometimes the Teams web app.

Same issues here on M1 MacBook Pro. Most of my company is Windows-based so I don’t think they endure as much pain.

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

#327

Post by X-Istence »

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

Earlier quoted context omitted.

My company uses Teams... and I wouldn't wish it on my worst enemy. So here's at least one person who is using teams who complains about it. The shitty UI/UX is one thing, but some of the behaviors are incredibly frustrating. Here's some examples: - 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 scree…

> 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 clicking on that little window all the goddamn time just so I can see my co-workers and know who is talking.

I don't want it to minimize at all. And I surely don't want it to sit in the bottom right corner and if I move it, move back there.

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

#328

Post by apnew »

treesknees wrote: post #199
apnew wrote: post #137

Earlier quoted context omitted.

Literally sitting here right now trying to figure out how to get simple things going compared to slack after being forced to move to teams from slack (not GitHub). I am all for dogfooding here, but if the dog-fooding is not improving the product it shows that the goal is to eat market because of lopsided ecosystem monopoly. Screw MS and MS Teams. eg. : We need a tag in a shared channel so that we can provide single p…

From the quote it appears the goal is to save money. From the numbers I found, GitHub could be paying upwards of $35k/month in licensing for Slack users. In a climate where companies are trying to shed expenses, wouldn't it make sense to bring that expense in-house?

I 100% agree with you about bringing that experience in-house.

My comment was reaction to the fact that there is a forced migration without 1:1 parity in feature set. Most large orgs/teams in my experience heavily rely on automation that has been added over the period of time reduce the cognitive load that is accidental/side-effect. Now if you are going to force them to move; give them a migration path.

Think of this in terms of API contracts. If half of the methods in your new version are not even available; why even make the new API public?

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

#329

Post by giantrobot »

wvenable wrote: post #218
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'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.

If I get a message on Teams and bring the window forward, the text box isn't active so if I start typing a reply nothing happens. Now I need to use the cursor to select the box. So fuck me if I tab to Teams to reply to a message.

When joining a video/audio meeting, even though the "Join" button is colored like it's active, hitting enter will pull up some part of the audio or video config instead of joining the meeting.

Messages will remain "unread" until a tab is selected and then clicked in. I have to interact with the fucking tab with the cursor before it will recognize I read a stupid message.

These UI issues are amateur hour shit. I run into them dozens of times a day because my fingers are on the keyboard and I like to use keyboard shortcuts. Using Teams requires not just a mental context switch but a physical adjustment to simply send a reply or just mark a message as read.

This is all besides Teams spinning up my fans with 300% CPU usage for reasons.

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

#330

Post by [deleted] »

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…

[deleted]
Post reply on HN