Hacker News Reader

Comment by robertlagrant | Hacker News Reader

Teams is doing well because it's often an IT department's simplest choice, but I don't find it's great for users.

The company I work for has a "Hours wasted because Teams sucks" page that gets updated at least weekly.

Eventually the list will grow so large that we could probably attach a 5-figure dollar amount to it, if it hasn't already.

Depending on the size of the company, that value is absolutely insignificant.

Bigcos with robust sales truly can’t afford the organizational-attentional cost of walking across the street to pick up a $10,000 coin.

/s ?

No, that’s really how it is. They leave opportunities to save or make five-figure (and larger) amounts all the time, because it’s not worth the distraction from other activities. And also from straight-up mis-management, but a lot of the time they know exactly what they’re doing, and it’s on purpose, and it’s probably not a mistake.

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.

> 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.

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.

The boat or the moat?

Reply on news.ycombinator.com