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

481–490 of 725 posts

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

#481

Post by thepostman0 »

ifyoubuildit wrote: post #365

Teams is dogshit in general, but the unforgivable part is that sometimes messages just don't show up until you restart the client. It's hard to know when this is happening, unless someone follows up on or refers to the missing message(s), but once you catch it a couple times it's hard to have any faith in the software at all. We've been told that this has been fixed, and it does seem more rare now, but I still end up…

For me it is the amount of ram it demands. Most of the day it is an IRC client, for a small portion it does voice/video. How does it need a gig of RAM all day? This squeezes my computer towards e-waste, and I'll be damned if I throw this computer away for an IRC client. Screw you MSFT, get it fixed.

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

#483

Post by generalk »

npteljes wrote: post #467
generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

>it's telling that Microsoft has to require folks to use Teams. Not really I think, considering that MS bought GitHub, with all of its already existing culture. I see this move as them homogenizing the infrastructure. And also not willing to pay to another company for a product that's actually their competition.

Of course, and I can't fault Microsoft for that, even if (having been on the bad end of a similar acquisition and IT merge) it sucks for GitHub.

My point was: GitHub as an organization didn't choose Teams willingly, and are still paying for Slack and only using Teams for video conferencing. Of all the explanations of why that might be, the easiest to land on is "because Teams just isn't that good."

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

#484

Post by twblalock »

Let's be honest, Slack sucks too. All of the solutions in this space suck.

Similarly, Jira sucks, but all alternatives to Jira also suck.

It seems kind of silly for Github to pay for another solution when they could use the in-house solution (which is Teams). This is what you have to compromise on when you let another company acquire you. People who don't like it need to leave -- that might not be how the world ought to work, but that's the reality and nothing anyone feels or says will change it.

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

#485

Post by chaostheory »

generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

Are your company’s MS instances on premise or cloud based? The reason I ask is because nearly all of the negative experiences I’ve had with Microsoft stem from either their native apps or poorly configured on premise servers.

This is anecdotal since there’s no wide ranging data, but Teams works just fine where I work. Integration with Outlook is also great, but we have a O365 plan that is completely managed and run from the cloud.

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

#486

Post by jms703 »

npteljes wrote: post #467
generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

>it's telling that Microsoft has to require folks to use Teams. Not really I think, considering that MS bought GitHub, with all of its already existing culture. I see this move as them homogenizing the infrastructure. And also not willing to pay to another company for a product that's actually their competition.

> not willing to pay to another company for a product that's actually their competition.

This. Companies are cutting costs. Teams may not be the best to use, but it doesn't make sense to have multiple chat solutions.

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

#487

Post by TulliusCicero »

twblalock wrote: post #484

Let's be honest, Slack sucks too. All of the solutions in this space suck. Similarly, Jira sucks, but all alternatives to Jira also suck. It seems kind of silly for Github to pay for another solution when they could use the in-house solution (which is Teams). This is what you have to compromise on when you let another company acquire you. People who don't like it need to leave -- that might not be how the world ought…

I don't use it for work, but I enjoy using Discord well enough for personal things (mostly gaming/tech, surprise surprise).

Every time I go from Discord to (full screen) Google Chat I cringe, it just feels so much more clunky for some reason. And I work at Google, so if anything I should be biased in its favor.

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

#488

Post by some_random »

twblalock wrote: post #484

Let's be honest, Slack sucks too. All of the solutions in this space suck. Similarly, Jira sucks, but all alternatives to Jira also suck. It seems kind of silly for Github to pay for another solution when they could use the in-house solution (which is Teams). This is what you have to compromise on when you let another company acquire you. People who don't like it need to leave -- that might not be how the world ought…

Slack sucks, Mattermost sucks, Discord sucks, but don't act like Teams doesn't suck notably more than the competition.

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

#489

Post by flangola7 »

twblalock wrote: post #484

Let's be honest, Slack sucks too. All of the solutions in this space suck. Similarly, Jira sucks, but all alternatives to Jira also suck. It seems kind of silly for Github to pay for another solution when they could use the in-house solution (which is Teams). This is what you have to compromise on when you let another company acquire you. People who don't like it need to leave -- that might not be how the world ought…

Slack is excellent! What don't you like about it?

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

#490

Post by lol768 »

ygjb wrote: post #209
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.

I will be blunt. Teams is an awful user experience; I have been using online collaboration tools since the BBS days, and while I appreciate and understand why and what they are trying to build, it is bad software. Every single experience I have had as a teams user in professional settings, interacting with communities, and being required to use it for interactions with my childrens schools since the 2020 shutdowns ha…

> If my employer required me to use it, I would immediately find another job. It's that bad.

Agree with this. I started adding clauses to my services contracts requiring that it not be used, to this end. One client moved over to Slack as a result.

Post reply on HN