Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Horror of Microsoft Teams

medium.com

Post reply on HN
Print view View original

121–130 of 344 posts

Re: The Horror of Microsoft Teams

#121

Post by senectus1 »

freeone3000 wrote: post #18
grezql wrote: post #14

Earlier 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.

Skype for Business (Lync) was discontinued in July, and support will stop July 31, 2021.

yeah thats not quite right: Microsoft announced that Skype for Business online will retire on July 31, 2021.

They still sell the product, and the hybrid/on premises solution is going to be around for a while. MS Teams will replace the "Online" only. There is no "on Premises" solution for Teams so S4B will be around a while I think.

Re: The Horror of Microsoft Teams

#122

Post by WiseWeasel »

addicted wrote: post #102
ptx wrote: post #94

Earlier quoted context omitted.

So essentially Microsoft's chat app is not good at chat, but you use it for file-sharing instead because Microsoft's file-sharing app is not good at file-sharing?

It's good at chat. It's not good at persistent chat rooms. It's great for ad hoc groups of people to chat or for direct chat. It's also great for meetings. Where it gets cumbersome is in the persistent chat room management. And as someone who is not a fan of chat rooms as a replacement for emails (I can't even filter or categorize information) I'm glad about that part.

Email is great and all, but not for regular topical discussions that may interest dynamic groups of people. A persistent, shared and searchable history and threading enables more effective discussion on a larger scale than practical with email.

Re: The Horror of Microsoft Teams

#124

Post by Macha »

evilotto wrote: post #103

At 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.

Just mute it would be a valid option if slack allowed whitelisting @here/@channel, rather than blacklist

Our slack instance has the opposite, a bot that explains how to mute in many "public" channels upon a here.

As is I need to remember to do the same every time I join or get added to a channel or some inconsiderate person on the other side of the world will @channel at a dumb time.

Re: The Horror of Microsoft Teams

#125

Post by mxuribe »

A Teams client for linux - meh. I mean, I guess I wouldn't mind it I guess (assuming I don't have to pay more for it per my office365 monthly fee), but i certainly don't seek it. On linux, I'm perfectly happy with libreoffice. However, what I do want is a native onedrive client for linux.

Re: The Horror of Microsoft Teams

#126

Post by pwarner »

johnbatch wrote: post #112
stuart78 wrote: post #20

At 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.

Yep

Re: The Horror of Microsoft Teams

#127

Post by alexandre_m »

throwaway7000 wrote: post #96

Disclosure: 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…

Been using Slack on a daily basis for work since 2015.

We have a fairly large group of users from different departments (IT, admins, engineers) of > 1500.

I would keep it succinct and say it's excellent. We're much more efficient at communicating than we used to be.

Re: The Horror of Microsoft Teams

#128

Post by Spooky23 »

johnbatch wrote: post #112
stuart78 wrote: post #20

At 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.

That’s why it’s a big electron app, it stitches together all of these disparate O365 components. It exists to empower the bureaucracy in a company to stop any migration away from their platform.

Users are pretty meh about it, but legal and compliance are big fans, because their process stays the same.

Re: The Horror of Microsoft Teams

#129

Post by zaphoyd »

bob1029 wrote: post #79

We 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…

RIP HipChat, last top tier native work chat program. We were paying customers for HipChat and were forced off when Atlassian killed it. Replaced by stride/slack/discord/teams all built on electron and all with awful non-native UI and web app like performance.

I know why they do it: electron is cheap and easy to spam on every platform. I don't know why: people pay for this crap.

Perhaps the issue is that people don't pay for it? Teams is free, bundled with other MS stuff that people are buying anyways. Discord is free. Slack is mostly free (until you are already stuck with it).

Re: The Horror of Microsoft Teams

#130

Post by mullingitover »

mysterydip wrote: post #120
mullingitover wrote: post #7

> "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.

Hah! I did this one at a call center job back in the day, not believing that their sysadmins would possibly leave it open.

I was wrong. I did something like "NET SEND lol" and it sent out a popup to every workstation on the network. Hundreds of them.

Good times.

Post reply on HN