My team has some users on Linux, and one benefit Slack has is a Linux client. Without a Linux client on Microsoft Teams, some orgs may have to turn away in favor of Slack so everyone can participate without keeping a browser open all the time.
We know many of you are waiting for a Teams client for Linux, and we’re pleased to confirm we’re actively working on it. Stay tuned for more information.
They tell us "It isn't forgotten", which is probably true. It's just been determined that it's more important to implement 'guest access' when I can't even get my entire INTERNAL team onto the service. This will never go anywhere without a Linux client.
Tell me again how we're still important to Microsoft? Because it sure feels like we've been given the short end of the stick...again.
I work for a multinational corporation with more than 70 000 employees. We have been curious about MS teams and the tests we have done on it make it a better fit for us than slack in many ways. The only problem right now is that there is no linux client. This forces us to stay with slack.
My company has about 80 employees, with 60+ of them involved in some way in software development or QA. _Most_ of these users are running Linux as their primary computers. The application works fine when it is run from the web using Chrome, so I do not see any valid reason that this cannot be exported as a desktop electron app. Microsoft refusing to complete this feature is just another demonstration of their contempt for their users, as the target audience for this tool (developers) is also the audience that is told that we're too unimportant to accommodate.
Most of our backend developers use Linux and our company clients use MS Teams. Linux MS Teams client would be very helpful in this situation.
Instead we must use Slack and appear.in to communicate with our clients for voice/video and www MS Teams client for text communication. It is really annoying. Please create a MS Teams linux client.
For a embedded SW development company, 50% of users on Linux is not unusual. Why can't MS make a version with IM and sharing functionality first, before worrying about voice call feature?
I like the features of MS Teams, but I'm going to be able to get my team on it unless there is a Linux client.
Jochem Fuchs commented
Just wanted to give the other people following this thread a heads up.
The webclient suddenly supports voice calls! No webcam support yet, but we can look at screenshares from others. I haven't tried screensharing myself yet, so that might still not work.
Anyway, It's enough for me to stop using a virtualbox to run Teams, so it's a step forward.
From the recent comments here it seems most people haven't noticed this feature change yet. So I'd thought to share it ( been there for at least two weeks now )
John Bettiol commented
Hello MS teams people!
This is a major topic for my company as we'd then have a single tool rather than a horrible hybrid slack/socialcast/s4b/appear.in situation
We are currently using slack, but, I am very disappointed that slack STILL hasn't fixed their issues with threaded comments on snippets/images.
If you manage to fix linux support BEFORE slack fixes threaded comments then it is very likely that we'll move to MS Teams.
Please re-focus on this topic, it is super-important for organisations that have non-MS developers to have a homogeneous communication platform.
Not having a full-featured linux client is undermining Microsoft's step forward with Visual Studio Code and preventing full adoption in IT. The longer we promote Teams and collaboration to the exclusion of developers, operators and admins on Linux desktops, the more we reinforce the pro-Microsoft business users vs. the anti-Microsoft technical users stereotype.
Tools aren't likely change people, but frankly Slack requires zero effort for adoption. In our organization, IT users are often the first to embrace, learn, champion, and disseminate new tools to the rest of the organization. Right now, Teams is stalled and our Linux users rely on Pidgin with SIP for Skype 'compatibility', but largely use private Slack channels.
[Deleted User] commented
This is an outrage! Just admit incompetence and defeat, you Microsoft scum!
Just GNU GPL your ******* software already, it's 2018 you're nowhere near having any unique or groudbreaking IP's. Everything you touch turns to ****. You have absolutely nothing but your 'brand' and shitloads of unmaintained and stinky code-bases.
If you're unable to do it yourself let someone else do it for you so that you can keep your brand without hampering your reputation further.
Barry Hughes commented
Well, that's killed Teams here then
Brent Watson commented
This is disappointing and on strengthens Slack grip on the number one place, which does have a Linux client.
Andrei Neagoe commented
As a few previous comments before, the priority can be lowered if the web client had better browser support and could be used for calls. That however, it's not the case...
it would be sufficient if there was usable(!) web client like Google Hangouts. We would not need desktop clients anymore.
James H. commented
It'd be nice, but the webclient in Chrome has worked well for me on Mint 17.1 for the last several months.
Absolutely need a Linux client for our developers ASAP.
https://github.com/ivelkov/teams-for-linux works great for the instancesI manage
Cool we'll keep Teams in the backlog and actively work on Slack. GG EZ
I’ve already lost the argument with our Linux toting slack users in our organisation. This seals the deal. How can I possibly get them back using Teams after this? It hurts me because they’re so damned vocal, and will use this as an example that “Microsoft hasn’t changed”etc etc. Perhaps they are right.
Joshua Clark commented
Visual Studio Code is already built with Electron, why isn't Teams???