Slack vs. Teams doesn't interest me as much as Teams vs. Hangouts Chat. Anyone here use both and can compare?
The Horror of Microsoft Teams
111–120 of 344 posts
Re: The Horror of Microsoft Teams
#112At my work, we use Teams a fair bit, and I'll go out on the limb to defend it (a limb I'm quite familiar with at this point ;) ). Thinking of it as a Slack alternative is, IMO, the wrong starting point. We barely use it for chat (as we have Slack as well). Instead, we use it as a file share and central information home. Each group within a team has a channel and we use the tabs to track meeting notes, embed external…
Doesn’t it just create SharePoint sites for each team on the backend and store the files in SharePoint?
Even on 1:1 chat sharing a file just uploads it to OneDrive and uses OneDrive links.
Re: The Horror of Microsoft Teams
#113At my org, you'd never know that slack has muting as an option. @here in a nontrivial channel gets you public humiliation, every possible "loud" reaction thrown at you (to the point of hitting the slack limit on reactions) and people publicly scolding you that you just notified 500 people in 12 different time zones.
I can relate to this. We have a few thousand people in our general channel. The channel description is:
Please do not use @ here in this channel. (You can mute this channel).
Re: The Horror of Microsoft Teams
#114We currently use Teams and everyone on the team absolutely hates it. I am actively looking at alternatives such as mattermost or slack to get us onto something that doesn't run like complete garbage. Also, why did this have to be developed using electron? If Teams were a native application, or even written using something on the .NET-side, we would probably have about 20% the complaints we do today. Watching an appli…
There are already a bunch of native Teams/Slack/etc.-like applications. Matrix has a good number of native clients[1]. There's Ripcord[2] which supports both Slack and Discord. There's Matterhorn[3] for Mattermost.
[1] https://matrix.org/clients/
Re: The Horror of Microsoft Teams
#115At my org, you'd never know that slack has muting as an option. @here in a nontrivial channel gets you public humiliation, every possible "loud" reaction thrown at you (to the point of hitting the slack limit on reactions) and people publicly scolding you that you just notified 500 people in 12 different time zones.
Workspace owners in Slack can set permissions on who can @here or @channel in a channel.
Re: The Horror of Microsoft Teams
#116We currently use Teams and everyone on the team absolutely hates it. I am actively looking at alternatives such as mattermost or slack to get us onto something that doesn't run like complete garbage. Also, why did this have to be developed using electron? If Teams were a native application, or even written using something on the .NET-side, we would probably have about 20% the complaints we do today. Watching an appli…
I'm convinced the community with never reach majority consensus on a solution.
Maybe people just suck at communicating?
Re: The Horror of Microsoft Teams
#117My team were using HipChat and had to find an alternative when they sold off to Slack. They actually offered a really good discount to move over. But as the company already recently moved to O365 and Teams is free within that, I thought I'd give it a try. My team hated it, I tolerated it. Until one day I'd just had enough of the UX that Teams brings. The biggest issue was the threading; it truly beggars belief. We en…
> That being said, the Teams UX will slowly and steadily improve You think that they people who brought us "The Word Ribbon" and Metro UI are going to make things better? That's not how M$FT rolls. Their customer base is deathly allergic to change. They lose their minds if things change perceptibly from what they looked like when they bought the system.
I don't know. The word ribbon was miserable to begin with but it has reached a point, thanks to a bunch of UI improvements, where it's far preferable to the classic menu for many people (at least the majority of people I've met).
The word ribbon is definitely an example to follow.
Metro isn't, because , wtf. They can't make up their mind.
Re: The Horror of Microsoft Teams
#118Earlier quoted context omitted.
We use teams at work. Most people i know cant stand it. Its chatoix UI. 10 tabs on each «teams». Ive deleted the app. Whenever someone tags me i just open their browser app, reply and close. Even having the tab open sometimes causes cpu and memory spike and my laptop fans starts wirring. If they kill skype/lync for teams, MS is making a huge mistake. Lync and Outlook are the most distraction free softwares we use.
Lync itself is decent from a UX standpoint. But holy fucking batman, the backend for Lync is an absolute nightmare to setup and maintain. I wouldn't blame Microsoft for wanting to get rid of Lync just to be rid of it.
what?
are you serious?
Lync and Skype for Business UX is an abomination. I rage every day any time I have to use it, and I've been using it for about 10 years.
Its the worse UX in any app I've ever had, I find GIMP easier to navigate than S4B.
Re: The Horror of Microsoft Teams
#119Disclosure: Microsoft employee. Using a throwaway. Satya, please don't track me down and fire me. I've never agreed so heavily with a headline and disagreed so vehemently with the actual content. Some of this is right, but a big chunk is wrong and I think misses some of the most egregious horrors of Teams. I used Slack professionally before in a fairly large org (>200). Two things the author got wrong: First - things…
I wholeheartedly agree with the emoji thing. Seems simple and unimportant but it's a way to communicate and teams is terrible at it.
the people who work on teams seem nice though, I actually got a helpful answer to my SO question about emojis:
https://stackoverflow.com/questions/53384141/teams-webhook-s...
oh and the formatting thing is a disaster. Something slack go so right - (markdown text input, styled on rendering), Teams gets so wrong (a way too easy to break rt javascript horror. entering code snippets is a nightmare, ` type something ` hope the "code" box pops up. `` right after each other - nope.)
Re: The Horror of Microsoft Teams
#120> "This means that if someone does @${channel_name} you will get an alert. MS have not implemented muting as a feature. Secondly, for all those automatic/admin channels, you can’t unsubscribe yourself (or at least not with the default policies). Brilliant, isn’t it? Unavoidable alerts that any idiot on any channel can annoy people with." At my last job we figured out the fastest way to get your company off Teams: add…
Reminds me of the NET SEND command in windows 2000-xp. Allowed sending a popup text message to specific (or all with a wildcard!) machines on a network.
Sure there were times where such a feature would be convenient ("server going down for maintenance, please save your work", etc), but overall ripe for abuse. They disabled it in a service pack and took it out altogether in subsequent versions.