News for hackers. Stuff that matters.
Re:Why Slack is inappropriate for open source communications by s73ver on Tuesday April 11, 2017 @12:31PM (#14089700)
"Feature wise slack doesn't really bring much new. It just has a good interface."

That's a pretty huge feature. Never underestimate how making something more usable increases it's popularity.

Re:Why Slack is inappropriate for open source communications by cat199 on Tuesday April 11, 2017 @02:04PM (#14090739)
Really - what is sooo unusable about IRC?

Get a good GUI client, enter some parameters into a text bar, click 'ok', then chat. exactly the same process as a web browser..

The real problem is the 'endless summer' of tablet-era people who confuse the 'interweb' with the 'internet'. There used to be much more general community advocacy and understanding of promoting open communications 'baked in' to the internet culture which has been eroded by crass commercialization - this is the real problem that needs to be attacked...

Re:Why Slack is inappropriate for open source communications by chrisseaton on Tuesday April 11, 2017 @03:19PM (#14091465)
Can you easily share multi-line code, formatted in a proportional font and syntax highlighted, in any IRC client? That's something I want to do almost every hour I'm working.
Re:Why Slack is inappropriate for open source communications by mburns on Tuesday April 11, 2017 @09:40PM (#14094093)
Some clients will intercept multi-line messages and let you POST the content to a pastebin. That way, supported clients show pretty-printed code and unsupported client just see a URL.

Ex: https://blog.irccloud.com/pastebins/

Re:Why Slack is inappropriate for open source communications by s73ver on Wednesday April 12, 2017 @12:43PM (#14099362)
And how do I know that everyone in the room is using such a client? I know that everyone using Slack will see the message as I intended it to be seen.