3 ms·
> Fair enough, but I would still argue that if somebody's posting enough code for that to matter, a link to a pastebin or a Github Gist, with syntax highlightin
by hombre_fatal 8y ago
> Fair enough, but I would still argue that if somebody's posting enough code for that to matter, a link to a pastebin or a Github Gist, with syntax highlighting, is a better solution.
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.
I'd argue that you don't need to post "enough code" to benefit from monospace or multiline support. A developer channel in IRC is full of one-liners that would be improved by monospace.
Also, as a heavy IRC user, it's pretty painful following code discussion through a bunch of external links.
Compare that to my developer-centric Slack channels like Elm lang's where short code snippets are used heavily and it's easy to see context, it's so much more convenient. And when someone does have enough code, they can use Slack's snippet feature.
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. :)
- jlarocco 8y ago> 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.