3 ms·

> Email has hefty overhead per message. I don't think that poster was talking about protocol innards, although kudos for you for having that knowledge, but per

> Email has hefty overhead per message. I don't think that poster was talking about protocol innards, although kudos for you for having that knowledge, but perhaps they were, but in terms of user experience, slack/group chat is very low cost in terms of requiring any sort of mental pause before sending the message, specifically as a cost for the message itself. So much so, that a type of usage of verbal diarrhea can occur, so as to caution oneself against such usage, a little bit of thought before sending messages is always advised. Specifically, if I can echo the primary differentiation, all you need to initiate a chat communication is a name and a message, that simplicity works a lot for people. I've used both e-mail and Slack, and a combination of both is great in my opinion, but the comparison can seen by an example message in my workflows (I don't use Slack anymore though): Slack: 1) Find user/group by name lookup 2) Hi X, QUESTION_TEXT. 3) When done conversation, write outro E-mail 1) Find user/group by name lookup, if user is not encoded in e-mail alias, query relevant databases 2) Write subject 3) Write intro, message, and outro From my experience the reply from Slack 2) vs. E-mail 3) is much faster in the former case.

e12e 7y ago
Interesting points. I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message - and very hard for the receiver to handle low-hundred conversations in a work-day - precisely because few(er) senders take the time to write a short, but dense message - and expect a reply-response dialogue "to quickly sort things out". Which is much harder to both do in parallell and concurrently when busy with more than one snowflake problem at a time. I'm sometimes shocked at how slowly things get done now, compared to when I worked a support desk in the early 2000s. But mostly I'm just a little sad at the overhead generated by chat.
- sombremesa 7y ago
  I'd be interested to see the effects of using a retention policy[0] to discourage the use of chat as a be-all and end-all. IIRC some companies actually do this. [0] https://slack.com/help/articles/203457187-Customize-message-and-file-retention-policies https://slack.com/help/articles/203457187-Customize-message-...
  - RockIslandLine 7y ago
    When I worked as a stock trader, all of our chats were logged as a matter of legality.
- ergothus 7y ago
  > I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message I think the crap is related to the amount of effort put into the message vs the medium. Making it easier/harder to send a message MIGHT change the quality, but I'd argue the decay of email over time was due to people failing to put in any effort DESPITE the minimum required. I recall a coworker back in the late 90s talking about their usenet program, that made them click through a "Warning: What you are about to send will be read by thousands of people. Are you sure you want to send it?" message (paraphrased from memory). He found it daunting and therefore bad, I thought it was properly daunting.

e12e 7y ago

Interesting points. I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message - and very hard for the receiver to handle low-hundred conversations in a work-day - precisely because few(er) senders take the time to write a short, but dense message - and expect a reply-response dialogue "to quickly sort things out". Which is much harder to both do in parallell and concurrently when busy with more than one snowflake problem at a time. I'm sometimes shocked at how slowly things get done now, compared to when I worked a support desk in the early 2000s. But mostly I'm just a little sad at the overhead generated by chat.

sombremesa 7y ago
I'd be interested to see the effects of using a retention policy[0] to discourage the use of chat as a be-all and end-all. IIRC some companies actually do this. [0] https://slack.com/help/articles/203457187-Customize-message-and-file-retention-policies https://slack.com/help/articles/203457187-Customize-message-...
- RockIslandLine 7y ago
  When I worked as a stock trader, all of our chats were logged as a matter of legality.
ergothus 7y ago
> I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message I think the crap is related to the amount of effort put into the message vs the medium. Making it easier/harder to send a message MIGHT change the quality, but I'd argue the decay of email over time was due to people failing to put in any effort DESPITE the minimum required. I recall a coworker back in the late 90s talking about their usenet program, that made them click through a "Warning: What you are about to send will be read by thousands of people. Are you sure you want to send it?" message (paraphrased from memory). He found it daunting and therefore bad, I thought it was properly daunting.