Starting in the CompuServe era, and ending in about 2001, I was a voluntary member of the MVPs for Windows programming. You would get swag, including a full MSDN subscription. My reason for joining this and for otherwise posting hopefully helpfully on forums was to lower the barrier to Windows programming.
I was idle vis-à-vis this by about 1999, and was excluded from the benefits as a result.
Then I posted on several threads within rec.autos.bmw and I got an extra year or two of benefits.
Because it comes 'free' with an Office365 subscription. Embrace (<<you are here), extend, extinguish.
It's usually 'management'. The same management that won't pay for developer tools (including Slack) because 'why do you need that when you can do 95% of your work in VSCode?' It's also usually the same sort of management that can do 95% of their documents in... VSCode and markdown. Or LibreOffice.
Having been in the position, on a corporate Active Directory network it very much easier to roll out Teams than anything else. It works fine at the kind of internal video calls that companies spend their days on.
I don't think M$ does much dogfooding. The kinds of issues I encounter being forced to use their pan-awfuly for work makes me very skeptical of this idea.
… when it works. And if you never have to change camera or microphone settings.
> and calendar integration.
The little notification that pops up telling you your meeting is about to start based on your calendar? The one you better not click in the first 5 or so seconds it's there, because then you'll end up with an error message that tells you absolutely nothing, have to go back to the chat, and try again?
Same reason MS used a Perforce fork instead of Source Safe. Because the dogfood tastes terrible.
One of the executives at the late, great, Sun Microsystems once dunked hard on Microsoft by saying, "At Sun we don't make dogfood. We prefer to refer to it as, 'flying our own airplanes.'"
It's not. It's an independent company, that's most likely going to IPO soon. Microsoft was reported to be in talks to acquire Discord at some point, but that never materialised.
So non-employees join and provide free support to other users without having to pay them.
Discord really needs some enterprise plan. I've been saying this for years, they can take down slack.
Starting in the CompuServe era, and ending in about 2001, I was a voluntary member of the MVPs for Windows programming. You would get swag, including a full MSDN subscription. My reason for joining this and for otherwise posting hopefully helpfully on forums was to lower the barrier to Windows programming.
I was idle vis-à-vis this by about 1999, and was excluded from the benefits as a result.
Then I posted on several threads within rec.autos.bmw and I got an extra year or two of benefits.
Why would anyone use Teams?
Because it comes 'free' with an Office365 subscription. Embrace (<<you are here), extend, extinguish.
It's usually 'management'. The same management that won't pay for developer tools (including Slack) because 'why do you need that when you can do 95% of your work in VSCode?' It's also usually the same sort of management that can do 95% of their documents in... VSCode and markdown. Or LibreOffice.
Microsoft products are only free if your time has no value.
Having been in the position, on a corporate Active Directory network it very much easier to roll out Teams than anything else. It works fine at the kind of internal video calls that companies spend their days on.
I don't think M$ does much dogfooding. The kinds of issues I encounter being forced to use their pan-awfuly for work makes me very skeptical of this idea.
I am for my day job. I still mourn slack and gsuite.
It is fairly ok for meetings and calendar integration.
It is dogshit at chatting, however.
> It is fairly ok for meetings
… when it works. And if you never have to change camera or microphone settings.
> and calendar integration.
The little notification that pops up telling you your meeting is about to start based on your calendar? The one you better not click in the first 5 or so seconds it's there, because then you'll end up with an error message that tells you absolutely nothing, have to go back to the chat, and try again?
No, it's not usable. For anything.
Same reason MS used a Perforce fork instead of Source Safe. Because the dogfood tastes terrible.
One of the executives at the late, great, Sun Microsystems once dunked hard on Microsoft by saying, "At Sun we don't make dogfood. We prefer to refer to it as, 'flying our own airplanes.'"
Dogfooding only works when the dog food is edible.
Microsoft employees largely use Macs, so no surprise.
All Microsoft employees I know either run Linux or Mac.
Discord is owned by Microsoft IIRC.
It's not. It's an independent company, that's most likely going to IPO soon. Microsoft was reported to be in talks to acquire Discord at some point, but that never materialised.