Is there a reason that companies don't just use discord?
The Horror of Microsoft Teams
211–220 of 344 posts
Re: The Horror of Microsoft Teams
#212The 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.…
Re: The Horror of Microsoft Teams
#213The 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.…
Re: The Horror of Microsoft Teams
#214In 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
#215I 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.
Re: The Horror of Microsoft Teams
#216Earlier 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).
Re: The Horror of Microsoft Teams
#217I 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…
Re: The Horror of Microsoft Teams
#218Earlier 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)
Re: The Horror of Microsoft Teams
#219Earlier 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 ;)
Re: The Horror of Microsoft Teams
#220The 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.…
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.