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

141–150 of 344 posts

Re: The Horror of Microsoft Teams

#141

Post by toxican »

realPubkey wrote: post #45
cryptozeus wrote: post #43

Interestingly we do not have issues like this within our company. Recently switched from emails to Ms team and have never used slack. We are pretty happy with ms team with for few reasons: screen share, seems video or audio call, great support on desktop and mobile app, connection with everything Microsoft like word, excel, onenote etc. we are greatly enjoying it.

How big is your company? Have you tried the search 'feature'?

I just want to know who thought it was a good idea to return results with zero context around them and no way to jump to that point in a conversation. Right now the best you can do is search to find a date, then scroll up until you hit that date (which takes forever, since it lazy loads the convo one "screen" at a time)

Re: The Horror of Microsoft Teams

#142

Post by CharlesW »

Insanity wrote: post #5

Teams is horribly unintuitive to use. The UI is much worse than Slack. Took me long to realise I was looking at the chat window and to follow along the threads..

> The UI is much worse than Slack.

In what way, have you found?

I ask because I use both daily, and I like Slack better in some ways and Teams better in others.

Re: The Horror of Microsoft Teams

#143

Post by snowwrestler »

acdha wrote: post #131
zaphoyd wrote: post #129

Earlier quoted context omitted.

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.

Apparently it was great simply because it was a native app. Who knew that was the top criteria for a work chat app.

Re: The Horror of Microsoft Teams

#144

Post by toxican »

Solar19 wrote: post #139

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 built on Electron and still no native Linux client. There's a web version, but you can't join meetings or screenshare. There are 3rd party wrappers for the web version that enable meetings, but you still can't screenshare.

At the very least their web version needs to have parity with the desktop application. It's 2019, browsers can handle voice chat and screensharing!

Re: The Horror of Microsoft Teams

#145

Post by Someone1234 »

wolfgke wrote: post #51
bluedino wrote: post #47

Microsoft ruins Skype, then tries making their own communication tool. Ugh. What is it again that Microsoft is getting such accolades for? Visual Studio Code is fantastic. Github is great, but they bought that. Office 365? OneDrive? I'll give you those. Hosted Exchange is a thorn in my side. Internet Explorer and Edge are (were?) both a joke. I don't have any experience with Azure. Xbox is great. Their server product…

> What is it again that Microsoft is getting such accolades for? Visual Studio Code is fantastic. Visual Studio is great.

For what? Legacy desktop developing?

We used Visual Studio daily. Everyone I speak to wants to switch to VS Code because we're tired of the laggy mess that is Visual Studio 2019. Even with no addons it stutters and micro-freezes all day long with medium-large solutions.

Somehow VS Code, an electron app(!), feels snappier than VS a native app. We're just waiting for feature party (and nothing special, just managing project files/solution files without editing the XML manually, better publishing, and similar C# debugging).

Re: The Horror of Microsoft Teams

#146

Post by untog »

Solar19 wrote: post #139

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

You can make an efficient Electron app, just look at VS Code.

Re: The Horror of Microsoft Teams

#147

Post by bla3 »

Solar19 wrote: post #139

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

I'm not a fan of electron, but it's possible to build fast apps with it. Teams who build slow apps with electron will likely build slow native apps as well. Slow software is usually not the tech stack, it's the team.

Re: The Horror of Microsoft Teams

#148

Post by noddingham »

I'm sorry but you've got to at least spell check if you're going to put something on the internet for others to read.

Regarding the content, "It can take half a day because of all the fiddly little options that are so easily forgotten". What? If you've really been a "long time" Outlook user, then this is 10 minutes. Half hour tops. But a half day? This makes me not take anything you say after that statement seriously.

And your complaints about teams are related to admin policies. Believe it or not enterprises actually have admins and policies regarding their desktops and tools.

Unfortunately this represents what I've come to expect from medium content.

Re: The Horror of Microsoft Teams

#149

Post by gitgud »

Solar19 wrote: post #139

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

This has been discussed many times here... of course running a Chrome instance is inefficient but in some cases that's acceptable. Especially for the gains in cross-platform compatibility and reliable user interfaces.

Almost no other platform can guarantee that a UI elements will look pretty much exactly the same on all different operating systems.

Most people don't mind the extra RAM consumption for some applications... as long as the app works!

Re: The Horror of Microsoft Teams

#150

Post by gitgud »

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.

Once students learnt the NET SEND command, the school was plagued with popups... IT security is an evolving thing I guess.
Post reply on HN