Earlier quoted context omitted.
From what I can tell, it's written in Electron. I assume they did this so that they could share the code base between desktop (win/mac), ios/android/winphone, and web -- keeping the features sets the same on all platforms. VS Code is the same way and that works beautifully on Mac. I expect that same for this. Disclaimer: I work for Microsoft (Azure) but have no relation to Office or Microsoft Teams.
Electron is complete shit, especially for long running processes. Might as well use the browser version.
Microsoft Teams, the new chat-based workspace in Office 365
171–180 of 247 posts
Re: Microsoft Teams, the new chat-based workspace in Office 365
#172The cheapest plan for Office 365 that includes this is the $5/user/month, which undercuts Slack's pricing. It also includes a bunch of other stuff that I'm far less excited about; I wish they had gone with a more a la carte approach. I'm not confident that I'll be able to easily integrate this with the identities that I routinely use. Also, it seems like an unwieldy name -- "I'll 'team' that to you", or "let's discus…
They are really stuck on this "team" term it seems. Probably something they plan on bundling with team foundation server/services
Re: Microsoft Teams, the new chat-based workspace in Office 365
#173Earlier quoted context omitted.
https://stratechery.com/2016/oracles-cloudy-future/ >Consider your typical Chief Information Officer in the pre-Cloud era: for various reasons she has bought in to some aspect of the Microsoft stack (likely Exchange). So, in order to support Exchange, the CIO must obviously buy Windows Server. And Windows Server includes Active Directory, so obviously that will be the identity service. However, now that the CIO has p…
I once worked for a very big company that decided to use Microsoft SharePoint to unify all the forms of communication that had developed over the years. They hired a Microsoft consultant to help them out and I was basically her assistant during the entire process. This consultant was pretty expensive. What I remember most is that she acted more like a salesperson than an actual help at getting SharePoint working in t…
Sharepoint by definition required an architect or someone to flesh it out. Microsoft is taking on that role of turning a skeleton into a body.
Their pricing is more like (a made up example): Exchange $2, Sharepoint $2, Skype $2, OR Everything + BI, Teams, Groups, Planner, Flow, PowerApps and whatever else they make/dreamup this week for $3. It makes no sense to buy 2 things from Microsoft over the bundle. The pricing is even more apparent when you look at their mobile management offerings, and its cheaper to buy 4 products than it is to buy 2. So now that you are "getting Teams and Planner for free" you might as well try using them before shelling out for Slack and Trello. Plus compliance worries are handled.
Also, it's fairly easy to "leave exchange and sharepoint document libraries" if your setup and permissions arent complicated. Microsoft is pulling an Apple, and abstracting the filesystem away so you use Planner directly to store planning data, in a proprietary, non exportable format, instead of having a storage locker to store files. These "freebies" exist to make it more painful to leave the ecosystem once you have them up and working. That said i am guessing most companies dont have a ton of buyin to things like Planner or PowerBI yet.
Re: Microsoft Teams, the new chat-based workspace in Office 365
#174Two really unique things I think this product does 1) The use of GIFs/memes. While this seems silly, it is actually a big deal because it lowers the formalization of communication. Having used this product, you just have much better free flowing conversation and many times these "fun" items help you get the message across significantly better (ex. asking for updates or bumping things can now be done in a funny way).…
Re: Microsoft Teams, the new chat-based workspace in Office 365
#175Earlier quoted context omitted.
I've got an evil grin on my face just thinking about Microsoft's response to Slack. I hope they respond and I hope they don't let me down -- there's a prime opportunity here.
They should just respond with a giphy gif.
Re: Microsoft Teams, the new chat-based workspace in Office 365
#176Earlier quoted context omitted.
probably means the buggy part. i worked at microsoft and one note worked great on windows but was shit on my mac. it wouldn't even sync properly
There are lot of missing features too - See "Key OneNote Features from Windows Missing on Mac" http://www.makeuseof.com/tag/essential-guide-onenote-mac/ It was extremely slow and buggy on android. It wouldn't sync
A notable feature that we're missing on Macs is recording in Skype for Business (aka Lync) meetings. We only have two Windows notebooks in our team of 20, so we have to rely on them joining every important meeting to capture a recording.
[1] Another part of the decision is WSL, which might enable me to abolish my work VM.
Re: Microsoft Teams, the new chat-based workspace in Office 365
#177Haven't tested Teams yet, but very shrewd move by Microsoft. They lead in the productivity suite with Office/Skype/Sharepoint etc in enterprises and a slack competitor which tightly integrates all their services is a wonderful addition. As someone mentioned on this thread, they could have picked a better name "Let me microsoft team it to you" sounds weird.
Re: Microsoft Teams, the new chat-based workspace in Office 365
#178Re: Microsoft Teams, the new chat-based workspace in Office 365
#179Can I setup MS Teams without IT Admin?
Re: Microsoft Teams, the new chat-based workspace in Office 365
#180Earlier quoted context omitted.
For many organizations, running something like RocketChat inhouse might be an alternative...I mean, how many of Slack's features add most of the value?
Then you have to provision hardware to run it and someone to set it up and admin it. And deal with backups and data retention, etc. Healthcare IT teams tend to run ridiculously lean. There's a much stronger business case for paying a few bucks per user/month than take up expensive and generally highly limited sysadmin time rolling your own.
Chat's may or may not be deemed business records by a prudent attorney and therefore it may be possible to not retain them for reasons similar to those under which computer logs are not maintained. That might make complying with non-realtime HIPAA requirements simpler.
Relative to IT requirements, the trend is toward much higher ratios of machines to IT staff due to virtualization and orchestration. I suspect that over time, healthcare organizations will get more containers.
Anyway, I was not thinking just about healthcare...nor thinking that lack of slack is one of the significant areas in which improvement is needed in the now.