[pwarner]

> Microsoft did, and Teams is by all reports a solid success.

Not sure if the author has used Teams.

But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.

[simfree]

Teams is shovelware. Force bundled, with questionably reliable messaging, okay video calling (if your organization policies don't break it), and a fairly useless Phone System component that misbehaves often.

Great for organizations that believe these forms of communication should be an afterthought that has rough edges and inconsistent reliability.

The recent changes to end webhook support, kill Linux desktop support and do yet another rewrite are inane. Don't expect features you use today in Teams to work in 2 years...

[icameron]

My org went all in on Teams over 6 years ago. Removed all PBX systems and desk phones. Pulled out Cisco phones from 20 offices. Ported all numbers to MS. By all accounts it was unremarkable to the end users, and when WFH mandates started it was seamless. Definitely a lot less IT support for configuring and troubleshooting a phone system too. There is far less downtime because Teams will ring through to your cell phone if the office internet is down or your laptop is off. That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions

[rchaud]

Maybe in 2020. Teams is the defacto IM app for enterprise now. It may not be to your liking, but most workplaces don't need apps to constantly be adding new features. They need videoconferencing, chat, meeting recording and AI transcription and note-taking. All synced with everyone's Outlook calendars and authenticated by the same SSO used org-wide. Teams has had all of those for years.

[tgv]

They're ending webhooks? Bummer. By the looks of it, they're going to introduce a more complex alternative. No, two, because why not. Why make something work when you can also make two things that work half, right?

[pwarner]

> Great for organizations that believe these forms of communication should be an afterthought

Yeah great for in person and email companies.

[wiether]

Direct webhooks have been removed but you can still use webhooks to send messages to Teams using PowerAutomate.

It's messier to set and maintain but it works as intended and also you can add more things to the workflow.

If you just want a URL to send json to, the new way is awful. But if you want to have more control, now you can.

Sometimes I like the PowerAutomate way, sometimes I hate it...

[darth_avocado]

We are being forced to dump slack for Teams. The only people who like Teams is Sales and Marketing for some reason. Not a single engineer likes this, and it will break every engineering convenience that exists on Slack.

[awesome_dude]

As an ENG - I REALLY dislike teams - but I also dislike Slack

Slack should be emails that have been arranged into different folders - it just doesn't vibe with me for much otherwise (oo look you have 200 channels on unread - or, if you are the reverse, ooo look 200 channels with people chatting and I have to check every single one of them :(

[steeleduncan]

Discord if you don't mind something proprietary, Mattermost or Rocketchat if you do, Zulip if you want something slightly different . . . and no doubt many other alternatives

Slack is easy to replace with something cheaper and better on a product or technical level. The network effects are strong of course, but they won't sustain it forever

[glerk]

Discord is a solid product. They just need to launch a simple business-friendly alternative UI without the teenager gamer aesthetics. I’m surprised they never tried going after the enterprise market.

[dgxyz]

Sod it all. Just give me a decent email client again.

Business instant messaging is electric shoulder tapping and that makes me want to punch people.

I literally feel Slack drains me every day.

[Muromec]

I use teams at work and it's okay. Not the best, not the worst, but okay piece of software. At least I have both the calendar and the videocall things in one app and see when the call starts, so I don't accidentally ADHD myself into missing it.

[viraptor]

Anything that accepts webhook integrations will be able to do this. I've got the Google calendar and meeting notifications on Slack, but it would be trivial to replicate with any two systems that have APIs available.

[simfree]

Exactly, no on is truly overjoyed with Teams. As shovelware goes it is passable, but that is a low bar

[cj]

> I thought Google might do this after not buying Slack

They did: Google Chat. It’s bundled with Google Workspace.

[figmert]

And it's worse than Teams

[tootie]

I guess I'm in the minority but I haven't noticed a significant variance in quality and features on any chat app I've used in the past 20 years. It seems like a thoroughly solved problem. Slack's "killer feature" was that they really streamlined onboarding which is feels neat the first time you do it. Otherwise, chat is chat. The biggest obstacle has always been getting everyone you need to talk to to agree on which platform to use.

[MattGaiser]

Yeah, I would be curious if there is anyone out there paying for Teams. Teams wins as Teams is free with your other Office stuff.

[MagicMoonlight]

What issues do you have with teams?

It works well and there’s nothing I can think of that I want in it. It’s just a video and chat app.

[vladvasiliu]

It's by and large the slowest, jankiest, laggiest software I use regularly. And I say that as someone who swears Adobe has added a bunch of sleeps in Lightroom.

On basic chat: it will sometimes scroll up when I get a new message, while I'm actively participating in that chat, so I need to scroll back down to read the new messages. Occasionally it flickers, for bonus points. It will not mark the chat as read if I'm on it without clicking on a different chat and coming back. It's the only software I use that, for some reason, has an effect on my typing accuracy. Don't even get me started on its handling of copy/paste. I'm also pretty sure there's some joke I just don't get around the search function.

For calls: it refuses to pick the correct microphone, and will sometimes mute it completely somehow (I lose the feedback in the headphones – I have a jabra headset that does this). This will even happen when I hang up a call and start another one right away. Other times it works well. My default mic is always my wired, always connected, headset mic. I don't use BT headsets that switch from music to communications or whatever depending on what I do, which could confuse the available / selected mics.

It drains my laptop's and iphone's battery like no tomorrow, even if I turn off video and only do voice chat, even if nobody has the camera on or shares a screen. Also, on Windows, for some reason it doesn't use the native notifications, but implements its own crappy ones – but this isn't that big of an issue, since I mostly disable them anyway.

All this is happening on both the "heavy" (heh) Windows client, and on chrome on Linux, both running on a fairly beefy new PC with gobs of RAM. Fun fact: the experience was exactly the same on my 5-year-old laptop with a U-series Intel CPU, so I don't think it's a resources problem.

[udfalkso]

Teams suffers from one giant problem. There is a totally odd, but understandable from tech debt perspective, segregation between “chats” and “teams” which makes it practically impossible to find everything. It’s a fatal flaw. Slack is beautifully simple and effective in comparison. Also, the reminder feature on slack is extremely useful to me personally and I miss it dearly in teams.

[misir]

Let me clear my cache after logging in twice to get the OOM fixed so I can finally login to show you what’s wrong with it over a teams call and hope it doesn’t logout and reload randomly during the call.

[pwarner]

The fundamental design choice of Teams teams channels makes channels unusable vs Slack channels. The chat part (outside channels) is OK. I've seen the metrics for our instance (10k users), the teams channel part is basically unused.

Does this matter? Yes, I think so for a chat first culture.

[miki123211]

Teams is definitely a solid success. It is by no means a good app. Those two things aren't the same.

Slack started with an aggressive "bottom up" approach, they made something actually good and got to worrying about the sales part later. You don't need sales as much when companies come to you, begging you for an actual contract that fulfills their enterprise requirements, knowing that rooting you out is almost impossible.

Teams went the other way, in typical Microsoft style. Microsoft sells it bundled with all the other Microsoft things it sells. Most companies want a Microsoft contract anyway, and have an established sales relationship with MS, so adopting Teams is a lot less compliance, integration and procurement work than adopting anything else. You don't need good UI if your sales strategy isn't predicated on users choosing you for UI.

And then there's Discord, which really isn't a bad work comms app if you're small enough not to need the compliance stuff. It gives you almost everything the big apps do for free, including unlimited calls, an advanced RBAC system, as many channels / messages as you want, a decent bot API (including media streaming), good notification management, multi-server / cross-organization support etc. They're actively disinterested in selling to businesses (which is what makes them so good, the features they paywall are the features needed by gamers, not serious professionals), but that also means you'll need to eventually migrate off of it when compliance requirements set in.

[lovich]

I thought Slack started as a failed game and they only pivoted when their in game chat proved popular. They still have game assets around like their 404 page iirc.

[moribunda]

Slack was a sluggish version of IRC... And somehow the world bought it.

[spprashant]

Its a solid success if you squint just at the adoption numbers they achieved by cross selling it.

[e12e]

Google gave us Wave - surely that's enough? /s

[outofpaper]

Lol it aas an admirable attempt at something new. I loved the interesting blend of messaging and document creation. It the code still lives on as an archived open project btw.

https://github.com/apache/incubator-retired-wave