1. Markdown support is a realtime state machine that often gets confused and ends up formatting half your post differently than intended.
2. Its worse on memory than slack.
3. I like threading conversations, but microsoft leaves a lot to be desired. You can't link to the middle of a thread. Someone posting to an unrelated thread can make your whole pane jump.
4. The client has oodles of unused whitespace which means that you can only show 5-6 messages on 1080p screen.
5. Compounding 4, notifications, chat, and calling all involve swapping the main frame which interrupts the workflow. This is made worse by swapping views can take seconds.
6. Video quality is not good (though about the same as skype). But there were other restrictions that were annoying like needing to be in a call already to share your screen. Limited options for group chat.
7. Poor integration with existing Active Directory deployments. None of my companies email groups were able to be ported in because that would make a full team which isn't necessarily what you want.
8. Teams have all of their channels public or all of their channels private. There's no way to make a point of contact channel for a team. Combined with (7) it can be very difficult to seek out a group of people vs a specific individual.
I use Teams with one of my customers and Slack for most of my customers. I personally prefer Slack but Teams seems to get better day by day. Teams has threads down better than slack which can make it more advantageous. I think slack is better when it comes to being involved in different projects with different customers. I also prefer the ease of onboarding people to slack.
Were a team of 40 and we are using teams. It does work pretty well for most things, and I like all of the integration options. We had been using Mattermost prior to switching and a few of us still use that instead. The biggest issue I have with teams is the markdown support is not good. It tries to format as you type instead of letting you type markdown and have a type/preview mode. I've raised this on their forum and it doesn't appear to be anything they want to fix either. If they fixed that issue I wouldn't have any complaints.
if Teams is the same account, it SHOULD be able to inter-operate with Skype business users, but everyone where I work has migrated to teams now. I happen to like a lot of the integrations, but was never much of a power user with slack, I used it before it had a/v chat and used the google hangouts integration back then.
One thing I REALLY wish Teams had was a dial-in option for Teams Meetings.
My company has some groups using Skype, and a few development teams, like mine, that are pilot testing Mattermost. But word on the street is that our IT department is looking to put everyone on Teams. Everyone I've talked to that uses Skype regularly hates it. My team seems to love Mattermost and I think it helps bring us together. I really hope Teams can keep up that feel at least on my team.
One factor for Teams (vs Slack or others) may be regulatory requirements (eg HIPAA). A quick perusal came down to "Slack Enterprise can be made HIPAA compliant" where I got the impression that Teams was a lot closer out of the box.
I'm in an academic lab that uses it, I think because it's included free with the university's 365 subscription. I prefer Slack, I find the channel organization and notification system more sensible and Teams to be a bit buggy. I also find that it's easier to miss messages in Teams with the way it collapses threads by default, but maybe I just haven't adapted yet from Slack's IRC/chatroom model.
Not an "important" issue, but I also miss the built-in emoji auto-complete.
Windows 3.0 had a file manager? I remember trying to use Windows 3.0. My memory is that file management was basically dropping down to the MS-DOS layer and using the DOS prompt to do it.
Yep, and even weirder Microsoft recently MIT licensed the source for the NT4 version of that file manager (with changes so it runs/compiles on modern Windows) https://github.com/Microsoft/winfile
Wild, IIRC, the NT version had an option to "unlock" files and show you who's accessing a given file... I also happened to like aspects better than later Explorer versions, here's hoping for some interesting enhancements and a better File Manager.
/cdn.vox-cdn.com/uploads/chorus_asset/file/15979212/Clippy_ShipIt.gif){kind=link}
I guess it wasn't meant to be made public?
[1]: https://github.com/OfficeDev/microsoft-teams-clippy-app