TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Is anyone using Microsoft Teams?

53 点作者 tuyguntn超过 8 年前
We are considering moving from Slack to Microsoft Teams, if anyone is using it here, can you share your experience with it?

14 条评论

rarrrrrr超过 8 年前
Microsoft is smart to build their own Outlook killer, and they certainly succeeded in freaking Slack out[1]. We (SpiderOak) evaluated teams as competitive research when building Semaphor [2] (our own end-to-end encrypted alternative to Slack&#x2F;HipChat.)<p>I found Teams to be a credible offering. It&#x27;s shortcomings are mostly about being very new (e.g. no linux client yet, some unpolished UI associated with window resizing.) The O365 integration is nice. The client seems to be built using Electron and TypeScript, and if the pace of development maintains I expect it will be a serious threat to Slack. Of course Slack and Teams require trusting the vendor with your unencrypted content.<p>[1] <a href="https:&#x2F;&#x2F;spideroak.com&#x2F;articles&#x2F;slacks-morning-after" rel="nofollow">https:&#x2F;&#x2F;spideroak.com&#x2F;articles&#x2F;slacks-morning-after</a><p>[2] <a href="https:&#x2F;&#x2F;spideroak.com&#x2F;solutions&#x2F;semaphor&#x2F;business&#x2F;tour" rel="nofollow">https:&#x2F;&#x2F;spideroak.com&#x2F;solutions&#x2F;semaphor&#x2F;business&#x2F;tour</a>
评论 #13349311 未加载
评论 #13348801 未加载
darklajid超过 8 年前
We&#x27;re using it. It is bad. Company just started to introduce Salck, MS announced this thing and we had to jump ship because everything they deliver is considered flawless in certain circles.<p>The mobile app is crap. There&#x27;s no Linux client. No 3rd party integration that I&#x27;ve seen so far. Lots of bugs and I highly doubt that this project will move&#x2F;improve at a VS Code level. A beta for your corporate communication needs.<p>The only upside? It might replace &quot;Skype for Business&quot; which is worse than almost anything else.<p>Sorry for the rant, but this is a very active issue in my day to day business right now. If I could, I&#x27;d stay the hell away from Teams.
评论 #13346902 未加载
评论 #13346953 未加载
评论 #13347112 未加载
评论 #13347249 未加载
评论 #13346992 未加载
评论 #13348565 未加载
donmatito超过 8 年前
My opinion(1), after playing a while with MS Teams:<p>The pros : the product is quite good, let say it is good enough and much better than the status quo of relying on emails or Whatsapp. It is integrated with the Office suite, and if I understand correctly, will be free for pro Office users. It has a handful of very interesting product decisions, like threaded replies and iframe apps.<p>The cons : MS Teams is not as polished as Slack, the UI (especially of the chat area) is not as clear. The installation&#x2F;onboarding is not as fluid. They have less apps and integrations (obviously, this is just the beginning).<p>My guess : MS Teams will not even begin to make a dent in the almost 100% market share of Slack among startups, agencies and similar small, agile groups. The whole Office ecosystem is simply to heavy, the UX is not as great, and some integrations might be missing. On the other hand, it might win big in the entreprise segment, where Slack is less present, and where being in the Office family is not seen as a drawback but actually an sign of solidity<p>(1) I am an independent dev, working on an app for their platform, so this is an educated guess based on my testing. I will enable Teams to connect with each other or with Slack teams through shared chat (www.smooz.io&#x2F;microsoft).
评论 #13347329 未加载
评论 #13346940 未加载
评论 #13346804 未加载
评论 #13346751 未加载
apapli超过 8 年前
Yes, adoption is still an issue for us as it is in a pre-release phase and we have too many options (yammer, email, outlook groups, slack etc) but it&#x27;s very promising. Once they officially launch it that will help (hopefully) provide a clearer product direction.<p>It&#x27;s pretty feature rich for an app in &quot;preview&quot;.<p>It&#x27;s also free, and I like the tabbed experience. Bringing in Microsoft Planner, some document libraries and PowerBI makes for a pretty compelling story.<p>Microsoft haters will never use it, but plenty of digital teams may get forced to use it if their IT team have already purchased Office365. And it&#x27;s not that bad once you forget it was made by Microsoft.<p>Slack ought to be worried.
评论 #13348593 未加载
px1999超过 8 年前
We&#x27;re slowly rolling it out to individual product teams in our small (~50 people) ms-based dev organisation. Things are going reasonably well.<p>We&#x27;d have picked slack over teams in a minute, though it has compliance issues making it unusable for us - slack is just more polished and has a lot more that you can get out of the box &#x2F; with plugins. That said, teams still has some great features for us, so we&#x27;ll stick with it for at least 2017. We&#x27;ve tried a few similar options before (primarily group chat) but they all had gaps &#x2F; issues that resulted in them being not as useful&#x2F;used as we&#x27;d have liked.<p>There are still a couple of massive gaps in teams for us:<p>* No on-premise TFS integration<p>* It seems that Office 365 is all or nothing - we can&#x27;t tie the o365 account to our primary email address without it messing up external email routing.<p>If you&#x27;re trying to replace a culture of email + some IM + files tucked away in some document management system that don&#x27;t get updated as frequently as they should, it&#x27;s a good start. If you&#x27;ve already got good communication then it&#x27;s less valuable.
评论 #13347163 未加载
pvdebbe超过 8 年前
Our company bought into Office 365 ecosystem and Teams was a natural choice to try. We haven&#x27;t used Slack or similar tool before.<p>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&#x27;t working for us to run ordinary SfB plus Teams, we had to drop it. Can&#x27;t say I&#x27;m overly depressed over this decision... ;)<p>If Teams&#x27;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&#x27;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).<p>There&#x27;s no info on what updates Teams has seen so we&#x27;ve kept to our original comm channels for the time being.
评论 #13348604 未加载
ndespres超过 8 年前
After using Slack on my team for about a year to get away from the annoyances of Lync&#x2F;Skype for Business, management made us shut it down for not being an approved product&#x2F;not defined by company policy&#x2F;contributing to team fragmentation across other depts who weren&#x27;t on it. Fair enough, I guess. We turned on Teams as it comes with our existing Office 365 subscription and we are much likelier to get approval to use it for cost and &quot;Microsoft is a known quantity&quot; reasons. I was excited for something that would finally help us transition into using anything better than Lync compabywide.<p>So I was disappointed with the chat experience, the notifications, the way my colleagues still using Lync wouldn&#x27;t consistently get my messages, and the way groups vs private messages are displayed. We all found it really frustrating to use.
herghost超过 8 年前
I&#x27;d be interested to know why any smaller orgs &#x2F; teams might consider moving since I see this as Microsoft&#x27;s way of cashing in the on the Enterprise market who are loosely aware of Slack but entirely comfortable with having it blocked.
sergiotapia超过 8 年前
I can&#x27;t even find their pricing page. Clicking Free Trial and they are already asking me for information when I don&#x27;t even know what it costs.<p>I guess it&#x27;s startup unfriendly and only marketed for enterprise.<p>What made you want to switch from Slack to Microsoft Teams? How large is your team? Curious to see the responses to this thread.
评论 #13346747 未加载
pducks32超过 8 年前
I once did Client work that required certain data protection practices. Can anyone speak to Microsofts draw in that regard. Is it up to the standard you need if you work at a hospital or something like that?
anondevel0per超过 8 年前
I switched from slack after 4 years and I honestly can&#x27;t say I&#x27;ve missed any features.
lucb1e超过 8 年前
Sounds like a good question for <a href="https:&#x2F;&#x2F;reddit.com&#x2F;r&#x2F;sysadmin" rel="nofollow">https:&#x2F;&#x2F;reddit.com&#x2F;r&#x2F;sysadmin</a><p>I don&#x27;t mind the discussion here, I just feel like you might reach a more specific and bigger audience there.
hiby007超过 8 年前
I think slack should charge on per user basis for any number or team, instead of having to pay for the same user in two different teams.<p>I also think there should be cheaper&#x2F;better competitor for slack in the market.
评论 #13346809 未加载
tiernano超过 8 年前
Yea. We moved to it in the office. We used ryver for a while, looked at slack, but, given we are on office365 and are a Microsoft shop, it was an easy move. So far, so good.