Hacker News Reader

Comment by zo1 | Hacker News Reader

Why would I choose Slack for my employees when Teams integrates so nicely with everything else in the "stack". Teams is leaps and bounds ahead already, and Slack really lost the boat many years ago.

Speaking of which, I'm going now to buy more Microsoft shares.

View on HN

I don't think I have ever heard someone favorably compare teams chat with slack before. Even when I worked at a company that used teams for video calls and MS for email and calendar and documents and what not, everyone used slack for chat.

I don't think anyone was sad that slack didn't integrate with the other MS services "stack".

You are choosing teams. What are your employees choosing? In my experience teams is a terrible mess and a company using it would exclude me from working for the company because they very likely don’t give a crap about the day to day experience of the employee.

Maybe because you value your employees being able to copy an image from your chat platform?

(Teams still can't copy images, instead you get a massive base64 block of text iirc)

I don't like that either, but I get it, it breaks the privacy of the sent message as messages have permissions attached to them.

Honestly, bugged me a few times before I just switched to using the snippet tool. I use it all the time anyways and this felt natural.

It's not base64 because of privacy, and using the snipping tool instead of just copying is not natural. Imagine opening a whole other program to copy some text you just highlighted.

> Why would I choose Slack for my employees when Teams integrates so nicely with everything else in the "stack".

Does it really though? In my experience teams has a buggy integration with other things in the stack.

And Teams itself ia massively buggy and a resource hog for the whole time I've used it.

The boat or the moat?

Reply on news.ycombinator.com