Microsoft Teams is Replacing Skype for Business To Put More Pressure on Slack (theverge.com) 135
An anonymous reader shares a report: Microsoft Teams isn't even a year old, but it's about to replace Skype for Business. At Microsoft's Ignite conference in Orlando, Florida today, the software giant is revealing that it plans to kill off Skype for Business in favor of Microsoft Teams. Skype for Business took over from Lync, Microsoft's previous business chat app, back in 2015. Microsoft's original Teams launch made it look obvious that Skype for Business would eventually disappear, given the fact that Teams integrates most of Skype's functionality already. Microsoft says it has been building a new Skype infrastructure that has been "evolving rapidly," and it will serve as the enterprise-grade service for voice, video, and meetings in Microsoft Teams. A new Skype for Business server will be available in the second half of 2018 for customers not ready to move to Teams, but Microsoft is pushing Office 365 users will to move over to Teams as the key communications client instead of relying on Skype for Business.
This is the exact opposite of what they should do. (Score:5, Insightful)
If I were a buisness that used Skype, I'd be pissed off and probably change to Slack, rather than change to Microsoft Teams.
Re: (Score:2)
I use Skype and Teams in my job and I can tell you one thing; Skype will not be missed...
that's because Microsoft already killed skype. It hasn't been since just before Microsoft bought it. And yet somehow it got worse.
Open source to the rescue! Use Diaspora. (Score:1)
If you need a communication platform for your team that's open source, then Diaspora [wikipedia.org] is surely the way to go. It's written in Ruby using Ruby on Rails, and the code is on GitHub [github.com], so it's using cutting edge technologies.
Re:This is the exact opposite of what they should (Score:5, Interesting)
I've been using Teams for a little bit at two of my clients - and I have to say Microsoft REALLY needs to improve the efficiency of Teams before they go fully replacing Skype. As soon as I run the fat-client app whether on Windows or Mac, it's a resource suck as bad as anything I have seen. It's like a really sad, slow version of Google Wave.
Re: (Score:2)
I'm not familiar with Teams, but Slack is dreadful in the area of resource usage as well.
It currently hogs 1.5GB of my memory, with just 4 teams (of which 1 is defunct and not used at all) and absolutely nothing fancy going on (one or two images shared each day is about it).
Re: (Score:2)
Yup. It's that bad and there is like zero traffic on it with one team. Just to have a presence in memory drags the machine. They really do have performance issues with it they need to address before expecting corps to deploy it.
Even if they said "Just go virtual" you'd still hear an ESX farm scream in terror as a group of people logged into their virtual desktops in the morning!
Re: (Score:2)
Hardly surprising given that Teams is an Electron application [thoughtstuff.co.uk]. This is also why #Slack is such a resource hog - it consumes about 1GB per Team because each team runs in its own extremely inefficient browser process.
I understand the desire for Write Once Run Anywhere but surely there are better platforms to use than Electron.
Re:This is the exact opposite of what they should (Score:5, Insightful)
I would say they should have named it 'Lync' again. Skype for business has been the most confusing thing to talk about, because it has *zero* to do with Skype, except in the minds of MS marketing people.
As a result you can't just say 'Skype' because people won't do the right thing, you always had to say 'Skype for Business' which is a misleading mouthful.
Re: (Score:2)
I would say they should have named it 'Lync' again. Skype for business has been the most confusing thing to talk about, because it has *zero* to do with Skype, except in the minds of MS marketing people.
As a result you can't just say 'Skype' because people won't do the right thing, you always had to say 'Skype for Business' which is a misleading mouthful.
I'm on a project now that involves a large S4B deployment and this is me at every single meeting. Skype for Business is stupid name so everyone just says Skype, then the discussion turns to original recipe Skype and some people already use 'Skype' so why are we deploying it again. Cue the explanations, rinse repeat for the last nine months...
Re: (Score:1, Informative)
They're not "replacing" anything. They're:
1) adding Teams functionality to Skype For Business, because SFB is a functional product and Teams is new functionality,
2) rebranding SFB as Teams, because SFB is a clunky name and everyone has hated the name since it replaced Lync, and
3) releasing a non-cloud server called Skype For Business Server, because there are large enterprises that want to host their own stuff for various legitimate reasons.
This announcement has the following impact on everyday users/IT wor
Re: (Score:3)
We have O365 and Skype here at work and we prefer Slack to S4B in every way. In fact, we're evaluating other options for conferencing because S4B sucks when trying to operate with those who are not using S4B externally.
I fully understand why Microsoft is trying to go down this route, as evidenced by our lack of faith in their offerings; however, I am not certain it's going to do much to help them "win", especially when people are already paying for their O365 subscriptions and having to double up and use ot
Re: (Score:2)
I fully understand why Microsoft is trying to go down this route
Yes, so do I. It is the latest of MS saying "Us Too!!!!!"
Re: (Score:2)
Re: (Score:2)
Re:This is the exact opposite of what they should (Score:4, Informative)
Have you ever used Skype for Business? It's a shitty app, and won't be missed in the slightest. If they just shut the entire fucking thing down today, I'd be thrilled.
It can't keep conversations synced across devices, if you've got multiple instances open (For example on your PC, a remote PC and your phone) it will randomly send a conversation to a device that you're not using and you won't see it until later, it freezes for about 30 seconds every time you get a new conversation, the audio cuts out constantly, when connected with bluetooth headset if and other app plays a sound Skype for business just completely shuts down all audio until the other sound is done.
The entire Lync/Skype for Business team should be fired.
Re: (Score:2)
Re: (Score:2)
If I were a buisness that used Skype, I'd be pissed off and probably change to Slack
If I were a business that used Skype, I'd wait and see and assess what it means, before jumping the gate and racing off in some unknown direction powered entirely by my own lack of information.
Re: (Score:2)
Re: (Score:2)
Skype from what I can figure out - it seems to be pretty much Lync with a revamped chat window.
It's not even revamped, it's just Lync rebranded. It has nothing to do with original recipe Skype.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Yeah good luck with that. Companies are the biggiest MS fanboys who killed the superior Novell Netware, Unix, and other products to one unifying Microsoft solution hoping it would cut down on costs and save them money.
Teams is Skype, Sharepoint, some chat application, and Slack?? I never even heard of it before. Has anyone else?
It is not from Microsoft so it will be ignored by the enterprise since MS has a similar option. Everyone uses Teams and Planner is the new rage so far this year
Re: (Score:2)
> Replacing a fully functional product that a company probably spent a lot of money hiring people to implement and integrate with the company network with another product just seems moronic.
I don't know any decision that MS made that was not moronic.
They're surviving by luck and circumstances (Windows and some of its products like Office) are already so prevalent that they cannot basically fail, at least not easily because all the apps are made for it.
But their innovation and decisions are probably the s
Re: (Score:2)
Re: (Score:2)
Even our Cisco chat tool is just XMPP underneath. It makes it easy to integrate into a host of services. IBM's "Sametime" is also in libpurple. I've used both and they're fairly good. At the minimum I can at least use my own chat client.
They used to buy products like Slack.. (Score:2)
...rebrand it "Microsoft Slack", and call it innovation. I guess that model doesn't work anymore, or they just don't have the cash/prestige/fear-factor to buy whatever they want anymore?
Re: (Score:2)
Well... they did buy Skype 6 years ago so probably the model doesn't work anymore. But I don't think it ever really did thou.
Re: (Score:2)
Basically MS' IM product has been terrible all along, and MS kept thinking it was a marketing problem rather than a technical one.
The result is the same basic project being paraded under new name after new name. Going from OCS to Lync wasn't such a bad brand move, it was less of a mouthful. Going from Lync to 'Skype for business' was terrible, since it was clearly just Lync renamed to look like Skype, but no technical relationship between the two.
I would not count on MS suddenly 'getting it' and producing
Microsoft Extinguishes Successful Products (Score:1)
I wonder when Microsoft will figure out that changing the brand of their products every 2 years and killing off products just makes customers confused and kills any momentum they may have had previously.
To make it better, they add 15 license models making it impossible to know cost or how to pay.
Downhill again (Score:1)
Lync was pretty good. Then they replaced it with Skype - made it a little bad. Then Skype for Business; worse. Then MS Office 365 Skype for Business which is horrible. Can't wait to see what Teams will be like
Re: (Score:2)
Lync was never replaced by Skype. It was rebranded Skype for Business. Lync/Skype for Business was always lagging functionality found elsewhere. Slack has just come on MS' radar as a target. The problem for MS, is that they know they need to compete, but don't really know why. Which is why they keep changing focus.
Re: (Score:1)
You are absolutely right. However, most of those features requires additional configuration/expenses and MS doesn't make it easy to get to them.
I use both Lync/SfB and Slack, and I can tell you, Slack just works. AND if Google gets its head out of its messaging crap, it would be loads better than Microsoft. I mean I have about a few ideas that would be game changers if Google just would ask me.
Re: (Score:2)
"doesn't make it easy to get to them" a per fect excuse for the end user to give up and use teams or at least thats how cisco sells their webex... you could do it in house... if you hired a CE for it and it alone.
Re: (Score:2)
CE is covered ....
requires additional configuration/ expenses
And so it begins... (Score:4, Interesting)
An office suite program is integral to the efficient functioning of just about any business. So now, predictably, Microsoft is using its newest version of Office to leverage other applications into accepting more and more of its programs. Identify what "Teams" does that "Skype for Business" doesn't (especially with respect to how much of your business will reside on Microsoft servers after the change), and that is the amount by which Microsoft has increased its hold on your company. I have no idea what those differences might be, but I have little doubt they exist.
Companies that opted for Libre Office are starting to look smarter and smarter, while those that took the easy route and "upgraded" to Win 10 and Office 365 ("All Your Cloud Are Belong To Us") are probably going to regret their choice sooner or later.
Re: (Score:1)
Powerpoint and VBA are the big reasons the world can't switch to LibreOffice.
One would think Powerpoint is low hanging fruit. And, after 20 years of VBA, I'm surprised there isn't an opensource equivalent.
Re: (Score:1)
Prezzi is a good (not perfect) replacement for most people wanting to do presentations.
Re: (Score:2)
Excellent point. It seems to me both Powerpoint and Prezzy have stayed pretty much the same for quite a while now. I'm not sure whether that's because they are pretty much doing their job properly, or because nobody's really interested in developing them further.
I would think that if the latter situation is true, then the Open Source application would be more likely to see further development when there's no really compelling business case to be made to invest resources in such a project.
Re: (Score:2)
Microsoft is using its newest version of Office to leverage other applications
High time traveller. Welcome to 2017. You must have missed a lot in the past 15 years.
(Personal advice: Go back. Things made more sense then).
Re: (Score:3)
I bet a lot of people call you a condescending prick, and politely request that you fuck off and die.
Perhaps you should accept their well-meant advice.
Re: (Score:2)
Not really, a lot of people have a sense of humour and the humility to see how stupid their statements are.
Re: (Score:2)
Companies that opted for Libre Office are starting to look smarter and smarter,
Keep dreaming. For all it's foibles, MS Office still shits on Libre Office if you are in any business with more than one person...
MS likely pushing an even more intrusive platform (Score:2)
Skype: Embrace and extinguish, not even extend (Score:1)
Re: (Score:1)
Your post points out the problem Microsoft actually has. They have two separate and distinct products that kinda sit in the same area. Its confusion and muddled messaging. Exactly the opposite considering they are messaging apps.
Re: (Score:2)
Errrr no. Skype is still Skype. The thing in Office 365 is Lync, with a name and a logo change. (even then only partial, it still is listed as lync.exe on my system)
Lync, Skype, ... (Score:2)
Microsoft needs to make up its damn mind about this.
We support several flavors of Lync and are transitioning to Skype for Business and NOW they are going to change it again?
Re: (Score:2)
Another option: stop using MS tools. There is so many other options (free and commercial).
Wait, what? (Score:2)
Re: (Score:3)
To be fair, Lync was a cool name. They should have kept it.
Every year at our company we switch IM clients... (Score:2)
Lync, then Skype, then Jabber, now Skype again. We also use Webex for meetings. I swear, it's always the corporate IT guys jockeying for something. Once they finally settle on something, then MS changes their direction.
Excel and other MS applications are getting slower and less stable.
This push to the cloud is getting quite annoying.
Has it been two years already? (Score:5, Funny)
Time for a chat client name change!
* Messenger
* Communicator
* Lync
* Skype for Business (as opposed to "Skype for Pleasure"?)
... and those are just the ones that are still in my Applications folder! I think there were a couple besides those as well. And those are just corporate clients -- I'm not even talking about MSN Messenger, Windows Live Messenger, etc etc etc. And some were for both, before there was a big division between corporate and regular IM clients. ("MSN Messenger" came with Office X for Mac.)
Oh yeah, NetMeeting -- anyone else remember that?
And I'm sure I'm still forgetting one or two more.
Re: (Score:2)
Parent was naming Microsoft's products. Cisco has also committed to Jabber and is not EOLing it any time soon.
If it ain't broke, don't fix it... again. (Score:1)
Seems like every time Microsoft touches something, it gets worse. Adding Microsoft to just about anything seems to equate to adding malvertising bloatware, and create no way for any decent feedback. I suppose the only question I have, is "when do they screw this up so badly, they buy Slack and kill that?"
I'm honestly all for (Score:3)
Microsoft replacing a bunch of their duplicate services with one service to rule them all... I just wish they would decide on one and stick with it for a while.
The constant renaming and shifting strategies from NetMeeting to Groove to Yammer to Lync to Skype to Teams is getting kind of annoying.
That and their general problems with naming products.. geesh..
question (Score:1)
Not even close (Score:1)
I work in an almost exclusively Microsoft shop and we've been using Slack for over a year to collaborate. Recently we tried Teams because it's nice to be able to use your Windows domain credentials for everything, instead of having yet another set just for Slack.
Teams didn't last one day, hell it didn't even last one HOUR, before we went back to Slack. Teams is so far behind in functionality - even basic functionality - that at this point it isn't even a competitor to Slack. For example, to upload a file in
Welcome to the Microsoft slashdot .. (Score:1)
Anything will be better than Skype for Business (Score:1)
This is Moronic (Score:1)
Re: (Score:2)
Russia has an even longer and bloodier history than the US. The czars were murderous hacks who considered their serf population as their own property. They brutalized all of their vassal states in the cold war. Stalin massacred hundreds of MILLIONS. Russia has the most blood on its hands, more than any other countr
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Or even... HOW this is pressure on Slack? The Article is the same title and they just mention that Slack was worried about Teams before. And now somehow the highlight of MS cannibalizing one of its own products (a 3rd time in this product) is Slack worrying more...
Re: (Score:3)
When a large corporation has multiple products in one space, it usually means one of two things: either they are pursuing distinct niches, or they have no major strategy for that market.
It also means that the development talent is divided into separate groups.
If Microsoft is killing Skype for Business to focus on Teams, that means they have identified their business communication product as an important market. They are probably consolidating their dev talent, and they are probably going to integrate and pr
Re: (Score:2)
Basically you are saying Teams vs Slack is worse than Skype + Teams vs Slack. I get that. But MS was already an entrenched IM vendor in the business world. Their primary competitor was themselves with LCS, OCS, Lync, Skype, and Teams. And the article should have just said "MS Communicator, new year, new name."
MS (and other big guys) talks about SaaS but then do stuff like this where its the same service but the branding has changed because the underlying technology comes from a different repo, code bas