3 ms·

Not sure what everyone issues are. I use Teams (in the browser) on Linux and it works fine under both X11 and Wayland (with some work). A bit less polished than

Not sure what everyone issues are. I use Teams (in the browser) on Linux and it works fine under both X11 and Wayland (with some work). A bit less polished than Slack but it also has a lot more features. The worse thing about the desktop/Electron version is that they are really bad about keeping the electron version updated so the browser version will support screen sharing on Wayland while the desktop app doesn't.

CharlesW 5y ago
In my experience, most people in engineering orgs default to hating Teams far more than it deserves. and loving Slack far more than it deserves. This has roots in Microsoft's history as computing Bad Guy and Slack's pre-Salesforce history as Scrappy Indie. Teams is more complex than Slack but also does more, but it's also not a complete superset of Slack, so unplanned/unguided transitions from Slack to Teams tend not to go well. Like any sort of knowledge management change, it can go well with empathy, planning, and care.
- iso1631 5y ago
  > Teams is more complex than Slack but also does more Perhaps that's the problem. I generally prefer the right tool for the right job, and once I have a tool that works, the effort to switch needs a compelling reason. Adding a "hammer" function to a screwdriver makes the screwdriver worse, it doesn't provide that compelling reason. Adding multi client access, stored chats, and even some formatting, were compelling reasons to switch to slack over irc.
spystath 5y ago
In reality the Linux and web versions are not similar to the actual Windows client. For instance the Linux version is stuck to 2×2 video streams at best, doesn't support background blurring, audio/video quality is inferior, doesn't support sharing a single window, no breakout rooms etc [0]. None of these are of any considerable importance to me but Linux or the web has never been priority for Teams nor will ever be. In fact I will not be surprised if/when Linux is dropped completely when transitioning to Webview2. Judging by the "PR-speak" [1] this is what probably will happen anyway. [0] https://microsoftteams.uservoice.com/forums/555103-public/suggestions/40324324-keep-the-linux-client-up-to-date-with-the-latest-f?page=1&per_page=20 https://microsoftteams.uservoice.com/forums/555103-public/su... [1] https://github.com/MicrosoftEdge/WebView2Feedback/issues/645#issuecomment-731474506 https://github.com/MicrosoftEdge/WebView2Feedback/issues/645...

CharlesW 5y ago

In my experience, most people in engineering orgs default to hating Teams far more than it deserves. and loving Slack far more than it deserves. This has roots in Microsoft's history as computing Bad Guy and Slack's pre-Salesforce history as Scrappy Indie. Teams is more complex than Slack but also does more, but it's also not a complete superset of Slack, so unplanned/unguided transitions from Slack to Teams tend not to go well. Like any sort of knowledge management change, it can go well with empathy, planning, and care.

iso1631 5y ago
> Teams is more complex than Slack but also does more Perhaps that's the problem. I generally prefer the right tool for the right job, and once I have a tool that works, the effort to switch needs a compelling reason. Adding a "hammer" function to a screwdriver makes the screwdriver worse, it doesn't provide that compelling reason. Adding multi client access, stored chats, and even some formatting, were compelling reasons to switch to slack over irc.

spystath 5y ago

In reality the Linux and web versions are not similar to the actual Windows client. For instance the Linux version is stuck to 2×2 video streams at best, doesn't support background blurring, audio/video quality is inferior, doesn't support sharing a single window, no breakout rooms etc [0]. None of these are of any considerable importance to me but Linux or the web has never been priority for Teams nor will ever be. In fact I will not be surprised if/when Linux is dropped completely when transitioning to Webview2. Judging by the "PR-speak" [1] this is what probably will happen anyway. [0] https://microsoftteams.uservoice.com/forums/555103-public/suggestions/40324324-keep-the-linux-client-up-to-date-with-the-latest-f?page=1&per_page=20 https://microsoftteams.uservoice.com/forums/555103-public/su... [1] https://github.com/MicrosoftEdge/WebView2Feedback/issues/645#issuecomment-731474506 https://github.com/MicrosoftEdge/WebView2Feedback/issues/645...