Not sure about that one. Teams is an absolute failure of a chat and audio/video calls app. I think, even if Microsoft tried they could not get it worse than it is currently.
While the development effort, skill, and time, that goes into building something like Discord is certainly significant, I feel it's certainly something Microsoft could have built given their resources and technical aptitude. What you can't buy is the inspiration, ideas, and culture that make something like Discord happen.
If it follows the inspiration and ethos of tools like Github and VSCode, I'll be really happy. Given Microsoft's shift in attitude over the past few years, I really hope that's the case.
This always come first over user's convenience. But the user experience of this tech is abhorrent, so I could see that Microsoft would like to fortify Discord with security features and sell it as Teams 2.0. This actually could work if done right...
I disagree fervently. At my current job the department has strong pushes to use these features amongst the teams and if they weren't there we could explore real solutions.
As it stands we're doing things like task tracking and taking meeting notes in teams and it's a terrible experience. I can't help but wonder what happens to that corporate data when teams eventually gets the axe
The only saving grace Teams has is it so reliably overheats my MacBook Air that no meeting can be over an hour long
- The history (scroll up) takes a lot to load (this is on 300mbit up/down and fast processor)
- html content in the chat totally hogs the processor
- Attachments takes forever to open internally. Not so large files like 4-5MB of log pretty much wreck it
- upload is hilariously slow (again 300mbit up/down)
- loading in browser requires an explicit login to microsoft account to open, instead of a generated link that actually works (to add some salt, my company requires 2FA for the MS login)
- audio quality issues, 'intelligent' (echo blocking algorithm kicks in wherever it wants), call drops. Esp. bad in group calls
- 'teams' chat gotta be a joke with each post forming its own thread, and you'd need to click to answer the proper one. Close to unusable feature that bears the name of the product
- Video sharing has a massive lag on screen sharing both on visual and startup time
- Blurred background algorithm is a massive flicker and it really resents people with green (t-)shirts
- Calling the phone, instead the desktop while working on the desktop. (Half of my team uses phone version as it's less buggy)
- One more: if you don't login the phone app, it will remind you to login every 3hours - until it gets uninstalled....
- As soon as I start a Videocall, the rest of the Application is almost completely unusable
- The Application uses 500MB of RAM after it has been idling with one message received in the last hourI've never understood this either. What is the purpose of the Teams tab? Why doesn't it show up where all the other conversations happen? It doesn't make any sense to me.
that's not my experience, especially with a much worse connection. Maybe I live closer to the server?
> 'teams' chat gotta be a joke with each post forming its own thread, and you'd need to click to answer the proper one. Close to unusable feature that bears the name of the product
Interestingly, I like this feature: it's different from a group chat where all discussion are mixed together, each subject has its own thread, so it's easier to follow. And each thread can be ignored
Plus when running multiple instances the call goes to the first instance
Meanwhile, Zoom works daily without issue.
Discord would be a completely different territory of getting the users to join rather than their bosses.
Nevertheless we know that the product is not that important. If all slack/zoom customers are migrated to Teams over night. The Teams product will keep most of its new users and will have a value for an acquisition, not because of its product, but because of its users.
So even though I disagree that MSFT could build the chat application itself, I agree with OP that what is bought is not linked to the actual product
I used to be absolutely in awe of the technology Skype had... got bought for $8+B back then and Microsoft managed to ruin the p2p part and stability/latency of the calls
It is widely used in this context and is highly profitable. The closest true competitor would be Google which lags far behind.
I'm not seeing anyone raise issues from within my organisations other than the engineering side of the business preferring slack.
I also use both as I'm a partner on the engineering side of the business but also run a large consulting pod - I really don't care which one anyone uses. I don't personally see Slack being better 'enough' to justify the effort of switching for those that are already on teams.
It would be a dark day indeed if we'd have to stop spamming memes while at work
Each and every tech worker I know loathes Teams with passion. On the upside it's like a common enemy so there's a small team building aspect to using it.
On the other hand, we're mostly using it for few page design doc, and have no idea what "final professional doc" or what "proper section numbers" are and why would anyone care.
But hard to point someone to the right place without decent numbering.