Live data from Hacker News

The Horror of Microsoft Teams

medium.com

211–220 of 344 posts

Re: The Horror of Microsoft Teams

#211

Is there a reason that companies don't just use discord?

Does it self host? Does it integrate with AD for authorization and authentication? What tools does it have to ensure GDPR compliance? Is it easy to centrally manage and for IT to set limitations for which users can do what?

Re: The Horror of Microsoft Teams

#212

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

Have you seen that picture with UI latency for code editors? I can't find the article but it is ridiculous that we have laggy software that uses insane amount of memory and CPU time. If we are serious about easing on the climate change we should start with bloatware that is the majority of the software industry nowadays.

Re: The Horror of Microsoft Teams

#213

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 a Slack clone. Slack is built on Electron so Teams must be.

Re: The Horror of Microsoft Teams

#214
The worst thing about Teams for me is the god-awful file managing solution. Everything shared actually goes in to the SharePoint backend, but changes made in Teams don't always carry over to SharePoint and vice versa.

In addition, moving folders and files is such a broken and unintuitive pain, there's no way to do it inside Teams, you have to go to SharePoint in your browser.

I'm sure everyone who has had the displeasure of using it agrees with me.

Re: The Horror of Microsoft Teams

#215
post #9

I think it's pretty, but it's also very, very, very notification-happy. My icon in my taskbar is almost constantly flashing with stuff I don't need to read, from teams I'm only remotely involved with. I just figured out I could turn the banners off last week, but still overall it's a very.... loud application. Wish I could write some kind of filtering rules.

The cynic in me says that’s how they got those “more than 13 million daily active users”, and there may be some truth in that. If your KPI is “daily active users”, and that’s measured by keys pressed and mouse clicks, getting everybody to click a few times is a win (for you)

Re: The Horror of Microsoft Teams

#216

Earlier quoted context omitted.

I don't use the windows partition on my laptop for this reason. Once Unity and my steam has Linux support, I never looked back. Only issue is Matlab sometimes.

Out of curiousity, what issue do you have with matlab under linux? I have found its linux version to be one of the most stable commercial/nonfree programs I have used under linux (ubuntu/centos).

Not OP but if I wouldn't rm ~/matlab_crash_dump* regularly it would be hundreds of them. Can't really pinpoint the problems, but most of the time it's graphics related. Possibly because it gets used remotely over VNC or X2Go, not sure. In comparison the windows version over RDP has like 0 problems, running pretty much the same code.

Re: The Horror of Microsoft Teams

#217

I don't know. A lot of these issues (and I must admit I totally lost interest at the point I got to the complaints about message threading, although I did skim to the end[1]) are really personal preference. Take message threading as an example: we use it all the time and it works well. I actually prefer it to Slack threads. My main beefs with Teams are: - Performance: it's just far too damn slow to switch views. - Aw…

Yeah I weirdly agree with this comment the most i started facing a customer has been on teams since it came out I have been using for about 8 weeks after years of slack and I would say switching performance is my biggest beef. I don’t know why general performance wasn’t more of a discussion in this post since most of the big complaints are really tied to how your space is setup.

Re: The Horror of Microsoft Teams

#218

Earlier quoted context omitted.

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)

Oh yes, so much agree - almost completely pointless to search for something in a chat and only see the one line that contains the search terms, none of the context chat around it - dumb dumb dumb.

Re: The Horror of Microsoft Teams

#219
post #166

Earlier quoted context omitted.

I caused havoc in high-school with that. And finding a way of executing binaries inside Novell's Netware thing, via the "Open" dialog within any Office application's Visual Basic macro editor haha

Renaming executables to explorer.exe worked with the application whitelisting solution my school implemented. That's how we ended up with 8-player age of empires 2 deathmatches after hours ;)

I created a directory with alt+255. It was an unprintable character and showed up last in any dir listing. At most it added an extra new line. That’s how I was one of the only students whose apps didn’t get caught during auditing.

Re: The Horror of Microsoft Teams

#220

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 makes sense for Teams. The app is a chat client, sure, but it also contains the entirety of Office 365 and a third-party app platform. Chats can have tabs with Excel documents, wikis, polls, etc.

By leveraging browser technology they have a platform that is incredibly extensible. Building that from scratch across iOS, Android, Windows and macOS is not feasible. And the benefit of having people reach to the tools at hand and strengthen Office's position outweighs the performance penalty.

Post reply on HN