3 ms·
For what it's worth, I like MS Teams... I'm not even a big Windows guy at this point... most of my dev at least targets linux, and most of my time is in VS Code
by tracker1 7y ago
For what it's worth, I like MS Teams... I'm not even a big Windows guy at this point... most of my dev at least targets linux, and most of my time is in VS Code with an ssh or wsl remote session. I use Linux directly, but not as much this past few weeks as a couple projects I'm on don't work in Linux.
I think that Teams is better than most at most of what it does... That's kind of hard to quantify, but like most things from MS Office, it's not that it's the best at any given one thing.. it's that it does many things good enough and things the competition doesn't.
- sebazzz 7y agoTeams is however _weird_ when it comes to files. Apparently a Teams team has a shadow sharepoint site behind it. The attachments from teams are stored there. However, when I want to embed an Excel sheet from the _actual_ Sharepoint site of my team, I have no way to do that.
- tracker1 7y agoThat I cannot speak to... I've only really used it either via teams and/or web ui and/or dropbox... What I do hate is that I can dump the wiki via onedrive, it's a goofy format, rather than simple markdown, and you can't update via onedrive (it doesn't go back to the wiki). Again, I don't think it's the best at anything... just a pretty good combination of things.
- WorldMaker 7y agoIt's not meant to be a "shadow" SharePoint site from what I gather, it is meant to be the same O365 SharePoint site as every thing else for the Team. My impression is that it may be really easy for O365 admins to misconfigure, though, especially in (likely) scenarios of migrating (or avoiding migrating) on-premises SharePoint sites to O365. Microsoft products are sometimes loved by IT departments because they have lots of configuration options; Microsoft is just really bad about leaving tons of footguns lying around in those configuration options, and IT departments apparently love footguns.