> Be wary of simply justifying why it's not the end of the world when a feature is missing, which is a much different argument. For example, I bet everyone who

> Be wary of simply justifying why it's not the end of the world when a feature is missing, which is a much different argument. For example, I bet everyone who uses IRC appreciates some sort of indication for when they are mentioned even though they could ctrl-f for their username every once in a while instead. FWIW, by default my IRC client notifies me when I've been mentioned. A benefit of using an open protocol is that people can develop different clients that cater to their needs. For code discussions I open a browser and an IRC window side by side. If I'm not paying attention to the conversation I just close the browser and don't have code snippets polluting the chat window. > But I feel like you can always respond to any feature someone likes with "but why not just [inferior solution], it's not that bad". These things simply add up. :) I feel that goes both ways, though. Just in this thread people have complained that Slack uses an absurd amount of resources and is proprietary, only to have the concerns sidelined as not important.