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

131–140 of 344 posts

Re: The Horror of Microsoft Teams

#131

Post by acdha »

zaphoyd wrote: post #129
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…

I’m curious what was so great about it: when we did the comparison even the Atlassian maintainers picked Slack.

Re: The Horror of Microsoft Teams

#133

Post by userbinator »

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…

It makes me want to spend an entire month's worth of weekends writing a native clone that no one will ever use.

If you ever do, I'd suggest doing the same with Slack might get far more attention, given that it has a publicly documented API as well as a few thirdparty clients already.

Also, why did this have to be developed using electron?

Probably because Web/JS developers are far more common and cheaper than native ones? Otherwise, even MS itself is saying "Win32 is the future":

https://news.ycombinator.com/item?id=19883351

Re: The Horror of Microsoft Teams

#134

Post by checktheorder »

inetknght wrote: post #35
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…

> we use it for file sharing File sharing: apparently still a problem almost four _decades_ after the Internet was invented.

Heck, it's still a problem with direct connections. Take the average Windows PC. Take the average Android phone. Take a USB cable. Plug them in together. Now copy a few thousand MP3s from the PC to the phone using nothing but stock Explorer and watch the transfer rate drop to about 1/1000th of what the wired connection should be capable of, because Microsoft made sure to assign their most inept, incapable, dumbest employees when they designed MTP.

Re: The Horror of Microsoft Teams

#135

Post by GFischer »

empath75 wrote: post #72

This thread should give some much needed perspective on all the people who assume MS is going to destroy slack. I bet slack destroys outlook before teams destroys slack.

As many mentioned, it´s licensing. My team had Slack but Teams got rolled company-wide and we were forced to switch.

IMO Teams is much worse but I guess it gets the job done not horribly enough.

Re: The Horror of Microsoft Teams

#136

Post by [deleted] »

ptx wrote: post #94
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…

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?

[deleted]

Re: The Horror of Microsoft Teams

#137

Post by joshschreuder »

dagw wrote: post #12
adzm wrote: post #6

I had the fun experience recently of having to rename a bunch of files that happened to have a # in the filename, since that character is forbidden in filenames that are uploaded into teams. Additionally, you can't seem to attach a .json file... though renaming it to .json.txt works. It's frustrating for sure. Thankfully they finally fixed some issues recently so I can copy chats out of Teams without running into too…

Additionally, you can't seem to attach a .json file... though renaming it to .json.txt works. It's frustrating for sure. Ran into something very similar during my (very) short stint doing Sharepoint development. I'm guessing it's some sort of limitation burried deep in some default MS code somewhere.

One of the comments above says Teams sets up a Sharepoint site for each team to upload files, so it's probably the same limitation.

Re: The Horror of Microsoft Teams

#138

Post by screye »

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…

That is what everyone I know uses it for too. It is almost like git, in how every sub team has their own private branch.

Honestly, any important discussion that gets too chatty for teams, should be a meeting.

That being said, everyone in my team generally sits on the same floor, so collaborating physically isn't an issue. I am sure a few of teams's shortcomings will become more evident once we start collaborating with remote teams.

Re: The Horror of Microsoft Teams

#139

Post by Solar19 »

The Teams client is built on Electron? Why?

Developers need to stop building slow applications. This is ridiculous. It's 2019 and software is slower than it was in the 90s.

It must take an enormous number of CPU cycles to execute simple tasks in an Election-based app. It's just incredibly inefficient. I heard similar things about Slack – that it was built on Node, maybe Electron, and was dog slow, especially to open. It's frustrating that developers are bringing the slowness of the web to the desktop. Just build proper desktop applications using native desktop APIs.

Re: The Horror of Microsoft Teams

#140

Post by CharlesW »

francisofascii wrote: post #132

Kind of related. I cannot login to Teams from home. Some sort of infinite redirect loop in both IE and Chrome on my home PC. It is pretty horrible.

FWIW, I'm using Teams from home as I type this, and I've never seen this come up as an issue in our (large-ish) company's communications channels. I don't believe you're experiencing a Teams problem.
Post reply on HN