Live data from Hacker News

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

twitter.com

71–80 of 725 posts

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

#71
post #37

What's the problem with "4 yr old laptops"? My colleagues and I use Teams on computers 1-5 years old and haven't heard about any issues.

Maybe that works well on Windows machines, on the Mac at least on the Intel-era some year-old Macs MS Teams is one of the most horrible, buggy, resource hungry, non-working app that one could imagine.

As soon as the M1 dropped, Apple just stopped giving a shit about Intel Macs. The whole OS is slow, janky, and appears to have driver bugs on Intel.

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

#72
How is it possible that Teams is still such a poor product? I really didn't like it when my job switched like 6 years ago, and I don't recall ever feeling that it improved in any meaningful way. I switched jobs to one using Slack and it's not perfect but it is a lot better.

It's almost a meme at this point. In the presence of other clients that have gotten it "right" (or at least more "right" than teams) like Slack, Discord to an extent, and Zoom for video calling, how has Microsoft allowed this festering wound to languish? Surely they could afford to revamp this product and reap the rewards of people not hating using their tools?

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

#73
post #13

Maybe I'm nuts, but I see almost zero appreciable difference between any of the most common chat or video conference platforms. They all have some little quirks or bonus features, but 99% of the time I'm only using the core features that they all do the same. Slack is absurdly expensive for what it does. Slack Pro is $12.50/person/mo. It's the same price for O365 which includes chat, video and the entire Office suite…

Nah, Zoom was wildly better than other options at first, but the rest these days are mostly OK enough to handle most day-to-day needs. And yeah, chat apps are pretty similar. ... except Teams, which manages to be possibly the single most confusing piece of software I've ever used. And I like Paradox games....

Zoom was amazingly batshit better than the competition (mainly gotomeeting) for actual conference calls because of how easy it was for someone who had never used it to start (which we later learned was because Zoom was pulling all sorts of clever bullshit to avoid installation dialogs).

Once you're past the onboarding/installation hurdle, they all start to blend together.

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

#74
post #37

What's the problem with "4 yr old laptops"? My colleagues and I use Teams on computers 1-5 years old and haven't heard about any issues.

Maybe that works well on Windows machines, on the Mac at least on the Intel-era some year-old Macs MS Teams is one of the most horrible, buggy, resource hungry, non-working app that one could imagine.

It's so bad it makes Slack look lightweight. Which is a real accomplishment.

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

#75

uh.. i dont see the problem? They are only using it for video conferencing. day to day collab still on slack...

Its like forced conversion. It only benefits MSFT. Teams get to claim github as a customer, and MSFT saves some money. This might be small, but usually this opens the door to a whole suite of software being shoved down github's work/tech stack.

This way they also don't send all their internal company communications to a third party, which would be extra stupid when you have your own in-house conferencing software to use instead.

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

#76

uh.. i dont see the problem? They are only using it for video conferencing. day to day collab still on slack...

Its like forced conversion. It only benefits MSFT. Teams get to claim github as a customer, and MSFT saves some money. This might be small, but usually this opens the door to a whole suite of software being shoved down github's work/tech stack.

I mean... it's a pretty hard sell to say "Hey boss person, can we use our competitor's software to discuss company business?"

My team also used Slack when I joined and were eventually required to move to Teams. We aren't forbidden from using Slack, I'm in multiple Slacks collaborating with various OSS projects and foundations every day.

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

#77

Earlier quoted context omitted.

You'd think but if where I work ever mandated I had to stop using Linux I'd start looking elsewhere. I have to spend 8 hours a day using a tool and I get frustrated with suboptimal tools, why subject myself to that on top of everything else I have to do.

For what it's worth, Teams is also available as a .deb/.rpm, which is I'd say unique for something with Microsoft in its name.

The teams .deb/.rpm sucks, and is an unmaintained electron app when MS temporarily "loving Linux".

If you want an optimal teams experience download edge and run the webapp in it.

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

#78

Next you must use office 365 for all documents and we will be moving to Sharepoint.

The single redeeming feature of Teams is that you can use it for documents and Sharepoint shit without ever having to actually open one drive or Sharepoint.

Until it inevitably breaks.

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

#79
post #51
post #2

That’s plenty of time to dust off the resume and start pounding the pavement! Very generous of Microsoft to give so much notice! Edit: for those who may think I’m overreacting to a small change in tooling, I offer this classic essay [1]. It explains the reasoning behind leaving much better than I could! [1] https://steveblank.com/2009/12/21/the-elves-leave-middle-ear...

[flagged]

Extremely-unpleasant tools can definitely contribute to leaving a company. I agree that it's a silly reason on its own, but it can be one factor of many—I mean, of course QOL at work is a factor in stay/leave decisions.
Post reply on HN