[ralusek]

Because it's good enough, has nice integrations, and is better than email. Convincing non-technical parts of my team to use a chat application is impossible if it can't go on their phones and is basically one single step to get going. Slack fits that criteria.

That being said, their notification logic. I remember seeing this insane flowchart demonstrating how complicated slack's logic was when determining whether to do a push notification. I wonder why it never occurred to them that one of the primary considerations should be that if you've sent me over 3 notifications in the past 5 minutes, and I haven't checked, please fucking stop.

[secabeen]

> I wonder why it never occurred to them that one of the primary considerations should be that if you've sent me over 3 notifications in the past 5 minutes, and I haven't checked, please fucking stop.

Because sometimes reading the notification is enough to get the information I need, and I want to keep watching the notifications, but I don't need to respond to any of them.

[sethammons]

This is an increasing problem with email too. If you don't open the email, you did not engage, so you can get removed from lists or, much worse, gmail will think something is spam. But gmail shows me most of the email in the UI next to the subject, so I don't need to open it. :sigh:

[2rsf]

> is better than email

You need to define better first, for many a-synchronous tasks or less-time-critical email is superior to Slack