I've seen teams rely only on Slack for communication, including technical discussions. I don't get it, and I'm concerned about the following: 1. proprietary s

I've seen teams rely only on Slack for communication, including technical discussions. I don't get it, and I'm concerned about the following: 1. proprietary service with no interoperability and high potential for loss of records 2. important technical details/arguments hidden in a chat log and not made part of a ticket/commit/comment 3. removal of async communication leading to more interruptions and less async emails one has thought about before responding 4. teams boasting the use of 10 or more channels There are other issues with relying solely on Slack and killing off email, but these are the most important ones that always come up when I'm confronted with a Slack-only team. I've had the same issue with IRC, so it's not my kind of communication medium to monitor 24/7, whereas I love bulk responding to emails and often ponder about a response for a while. If there's something urgent, one picks up the phone, and usually one thinks twice before calling (interrupting) someone. Using proper email threads, ticket discussions, etc. give you an electronic trail of the technical decision, and that's also why Fossil's inclusion of a distributed ticket system is such a great idea. Two years later, you can easily inspect how the code evolved and why it did in a certain way. How do dev teams cope with Slack? I couldn't work without async email and use real time communications (text or voice) only on demand, in order to limit interruptions.