Viewing a single comment thread. View all comments

DrabDonut t1_je5md3t wrote

Reply to comment by HiImDan in Microsoft promises it’s made Teams less confusing by unnamedprydonian

Teams exists for orgs that want most of their software licensing stuff dealt with through a single company. Why pay for Slack when you already pay for Office 365 and a bunch of other Microsoft services and you can simply add one more to the bill?

8

Xhiel_WRA t1_je5x0i5 wrote

It also exists as a solution for meetings, VoIP, etc. via a single app.

If you're actually using all of Teams' features, slack couldn't hope to realistically replace it.

If you're just using what Teams presents itself initially, slack is an obviously better choice.

Source: I work in an environment that is Microsoft bound for all software and teams is capable of some truly astonishing shit, but like 1% of people actually use it that way.

12

DrabDonut t1_je5xwqc wrote

Slack also has meetings and voip, but most people don’t use it as far as I can tell. I think it’s one of the things they’re struggling with user adoption of.

8

Xhiel_WRA t1_je5y5uq wrote

Case in point: I didn't even know that until you told me. Yeesh.

3

tiboodchat t1_je75l63 wrote

Afaik Slack does not have VoIP in the sense that it’s not an actual SIP service. And if it does I’d love for someone to point to where in the documentation cause it could be really useful for different integrations (am programmer).

2

Xhiel_WRA t1_je7d9yc wrote

A few scant minutes in Google tells me that slack does auto dialing and that's about it. Glad I didn't say anything about Slack VOIP to anyone other than reddit.

1

emote_control t1_je79eor wrote

Slack is buggy as hell though. There's one guy on my team who insists on video calls on slack "because it's easier, and we're already chatting on slack" and half the time it can't find my audio devices, or won't connect. We also use WebEx, which used to be terrible but got much better.

1

humorous_ t1_je5y2kp wrote

It’s the logical conclusion to the “Skype for Business” hole they were scrambling to fill for a couple years between Microsoft’s acquisition of Skype and the advent of Teams. The core idea behind Teams is probably the first Microsoft idea I’ve liked in a while.

Between Teams and O365, Microsoft pretty successfully pivoted into a business services titan rather than just the company selling the software businesses use. Plus now they can probably sell your data (or anonymized versions of it) AND charge you for using the services that collect that data.

4

Xhiel_WRA t1_je5yofl wrote

It's not just the logical conclusion, as in they naturally developed on into the other. No, no. SFB just fucking turned into Teams one day.

If you used Skype for Business (and didn't pay M$ to keep it the fuck still for another year while you desperately try to get out from under technical debt) your SFB turned into Teams, as in the client un-installed itself and installed Teams.

Your DNS records for SFB sip? Yeah they didn't need to be changed or anything. They just work for Teams. Same infrastructure.

2

humorous_ t1_je6c2z9 wrote

You’re right, I was misremembering the transition as less chaotic than it actually was.

2

Xhiel_WRA t1_je6eemn wrote

God it was a whole thing. /r/SysAdmin had some fucking incredible threads with people figuring out how to roll back, how to unfuck Teams, etc.

It was a wild time to be alive and working in the industry.

2