News for hackers. Stuff that matters.
Re:Slack client for the terminal by Karunamon on Thursday March 01, 2018 @03:37PM (#16496024)
How is this Slack's fault, again? Or is the argument that messaging systems should be hard to install so they aren't misused?

Seriously, what even is this comment chain getting at? If you work somewhere where always-on is a hard requirement, it doesn't matter what messaging system is used. Any place that would fire you for muting notifications would just as easily fire you for turning off email notifications.

In short: Let's stop blaming the damn tool for something that is the fault of the humans using it.

Re:Slack client for the terminal by tachyoff on Thursday March 01, 2018 @03:52PM (#16496212)
I’m blaming both: I’m blaming the humans who expect it, and the billion-dollar blob of JavaScript that enables it to be so.
Re:Slack client for the terminal by gsich on Thursday March 01, 2018 @03:43PM (#16496101)
Probably because Slack makes it easier to establish an "always-on" culture.
Re:Slack client for the terminal by Karunamon on Thursday March 01, 2018 @03:53PM (#16496223)
Literally any other instant messaging program would have the same effect if the culture is toxic enough to allow it.

Slack is no different other than name recognition and size.

Re:Slack client for the terminal by gsich on Thursday March 01, 2018 @04:42PM (#16496661)
Other instant messenger are primarly (yes, some companies probably use Whatsapp and co for work stuff) for family and friends. "always-on" is different here.

Slack is focused on business.

Re:Slack client for the terminal by tomc1985 on Thursday March 01, 2018 @04:35PM (#16496588)
I hate Slack too but the same could have been said for Skype, MSN Messenger, ICQ, or AIM...