4 ms·

Our company bought into Office 365 ecosystem and Teams was a natural choice to try. We haven't used Slack or similar tool before. Well, Teams allows discussion

by pvdebbe 10y ago

Our company bought into Office 365 ecosystem and Teams was a natural choice to try. We haven't used Slack or similar tool before. Well, Teams allows discussions, but at least in November its built-in Skype for Business (SfB) client worked exactly like the other SfB clients work: not at all well with others. (Serious issues with race conditions on how the server sends the messages to what client, with several listening clients everything turns into a mess!) Given that it wasn't working for us to run ordinary SfB plus Teams, we had to drop it. Can't say I'm overly depressed over this decision... ;) If Teams's SfB client gains the features the original SfB lacks, or alternatively if Teams would allow to disable SfB part of the software altogether, it might have been workable. I personally didn't like the intrinsic delays the chat process have unlike say IRC (feels very much realtime even though the delays are there under the surface). There's no info on what updates Teams has seen so we've kept to our original comm channels for the time being.

basch 10y ago
>(Serious issues with race conditions on how the server sends the messages to what client, with several listening clients everything turns into a mess!) This makes the mobile client nearly unusable in its current incarnation. I can be sitting on Facebook on my desktop and Messenger on my phone and alternate each sentence between each device. I cannot pick up my phone and continue a Skype for Business conversation I was just having on my desktop. Cant transfer the existing conversation at all. It is almost, nearly, surprising how ill conceived and poorly executed the experience is. I end up switching back to outlook when a person and I want to have a conversation while we constantly bounce between devices, because our email works and syncs everywhere perfectly.
- pvdebbe 10y ago
  SfB (Lync) is terribly done in terms of the client-server architecture. Messages don't get consistently saved for offline recipients, the issues with several listening clients. For a business communications application, it sure seems a lot less suitable for business/corporate use than Skype Personal. Yammer's another fiasco. Teams, on the other hand, might turn out to be very decent but the SfB integration brings it down.

by pvdebbe 10y ago

basch 10y ago

>(Serious issues with race conditions on how the server sends the messages to what client, with several listening clients everything turns into a mess!) This makes the mobile client nearly unusable in its current incarnation. I can be sitting on Facebook on my desktop and Messenger on my phone and alternate each sentence between each device. I cannot pick up my phone and continue a Skype for Business conversation I was just having on my desktop. Cant transfer the existing conversation at all. It is almost, nearly, surprising how ill conceived and poorly executed the experience is. I end up switching back to outlook when a person and I want to have a conversation while we constantly bounce between devices, because our email works and syncs everywhere perfectly.

pvdebbe 10y ago
SfB (Lync) is terribly done in terms of the client-server architecture. Messages don't get consistently saved for offline recipients, the issues with several listening clients. For a business communications application, it sure seems a lot less suitable for business/corporate use than Skype Personal. Yammer's another fiasco. Teams, on the other hand, might turn out to be very decent but the SfB integration brings it down.