Ask HN: How do you feel about Slack developer communities?
69 comments
My experience with these communities is that they are very close to non-functional, for several reasons. I use paid Slack, to pretty good effect, every day at work.
First of all, they have to rely heavily on hacks to store information long-term because of the 10,000 message limit.
Second, even with fairly diligent use of Google Docs for important stuff, tons of info is still lost. I've got a slack where I have DMs with four different people starred. But for two of the four, I have no idea why, because I don't recognize the names and the entire conversation history is gone.
Third, where the message limit is less of an issue, and low barrier to entry is important -- ones with a lower activity rate, and where the community is not super close-knit -- tend to suffer from constant challenges to the group's norms. People drift in and out, wanting to argue again and again about how it's OK for them to use exclusively male pronouns all the time, or how it's OK for them to discuss irrelevant topics. This takes up a ton of the message history, and lowers the information density.
Like it or not, IRC, with a web client, and a publicly available archive that is searchable, is far more functional for this situation. Paid Slack is a pretty good tool for work communication, but the free version, for now, doesn't translate well to open communities.
First of all, they have to rely heavily on hacks to store information long-term because of the 10,000 message limit.
Second, even with fairly diligent use of Google Docs for important stuff, tons of info is still lost. I've got a slack where I have DMs with four different people starred. But for two of the four, I have no idea why, because I don't recognize the names and the entire conversation history is gone.
Third, where the message limit is less of an issue, and low barrier to entry is important -- ones with a lower activity rate, and where the community is not super close-knit -- tend to suffer from constant challenges to the group's norms. People drift in and out, wanting to argue again and again about how it's OK for them to use exclusively male pronouns all the time, or how it's OK for them to discuss irrelevant topics. This takes up a ton of the message history, and lowers the information density.
Like it or not, IRC, with a web client, and a publicly available archive that is searchable, is far more functional for this situation. Paid Slack is a pretty good tool for work communication, but the free version, for now, doesn't translate well to open communities.
> My experience with these communities is that they are very close to non-functional
I had really good luck with the Elixir Slack channel when I was first starting out with the language. I guess I'd say Slack can be a great newb friendly place to ask dumb questions. There were plenty of times I didn't know what to Google, because I didn't understand a basic concept, and I couldn't figure out how ask a clear question on StackOverflow. When you're in newb territory, having a Slack channel full of helpful people is nice.
I had really good luck with the Elixir Slack channel when I was first starting out with the language. I guess I'd say Slack can be a great newb friendly place to ask dumb questions. There were plenty of times I didn't know what to Google, because I didn't understand a basic concept, and I couldn't figure out how ask a clear question on StackOverflow. When you're in newb territory, having a Slack channel full of helpful people is nice.
I don't disagree with this at all -- but the value there has very little to do with the tool, Slack. An IRC channel is at least as functional.
It's been years since I used Stack Overflow chat, but I always felt if it had been a bit better, it would have been the tool for groups like this. A missed opportunity, given that Stack Exchange is committed to making all of the information on their sites freely available forever, and Slack definitely is not.
It's been years since I used Stack Overflow chat, but I always felt if it had been a bit better, it would have been the tool for groups like this. A missed opportunity, given that Stack Exchange is committed to making all of the information on their sites freely available forever, and Slack definitely is not.
> When you're in newb territory, having a Slack channel full of helpful people is nice.
Exactly my experience as well. In those cases, Slack is just like an old school IRC channel with a shinier interface.
Exactly my experience as well. In those cases, Slack is just like an old school IRC channel with a shinier interface.
You both missed the point, which is - for such use cases, Slack is even worse than an old school IRC.
Well, in those cases you go where the community is. Maybe one is better than the other, but my personal preference doesn't matter here. I would still use one or the other, regardless. If something better comes along, you should use it.
Wouldn’t the same message history hacks apply to IRC? It’s an ephemeral platform by nature, so unless you have a bot logging conversations somewhere, it’s the same problem either way.
I am an IRC operator of nearly 20 years; and I guess I'm here to say: "it depends".
Speaking about IRC as if all IRC servers that came before are all IRC is capable of is.. odd.. it would be trivial to create an inspircd module that pushed data into elasticsearch.. At the same time, clients log by default too, they just don't expose a way of searching the logs they generate..
IRC is a (dated, stateful connection based) protocol; nothing more, it's a shame there are not nicer clients because of all the functionality slack has; are easily "add"-able to IRC, bar one- it's ability to handle network disconnections well.
IRC+Bouncer is how most people interact with IRC today; however it's a workaround for a problem users should not have.
There is a company called IRCCloud who are attempting to make IRC easy to use, much in the way slack do by operating a webclient+bouncer bundle for you.. You could also self-host something like "The Lounge" which does effectively the same thing: https://github.com/thelounge (I am not affiliated with either).
However I'm aware that the above options are both significant barriers to entry when compared to slack. that is the _real_ value of slack, onboarding people into a slack discussion is a breeze, and once you have someone there there's no tangible reason to move to something else.
Speaking about IRC as if all IRC servers that came before are all IRC is capable of is.. odd.. it would be trivial to create an inspircd module that pushed data into elasticsearch.. At the same time, clients log by default too, they just don't expose a way of searching the logs they generate..
IRC is a (dated, stateful connection based) protocol; nothing more, it's a shame there are not nicer clients because of all the functionality slack has; are easily "add"-able to IRC, bar one- it's ability to handle network disconnections well.
IRC+Bouncer is how most people interact with IRC today; however it's a workaround for a problem users should not have.
There is a company called IRCCloud who are attempting to make IRC easy to use, much in the way slack do by operating a webclient+bouncer bundle for you.. You could also self-host something like "The Lounge" which does effectively the same thing: https://github.com/thelounge (I am not affiliated with either).
However I'm aware that the above options are both significant barriers to entry when compared to slack. that is the _real_ value of slack, onboarding people into a slack discussion is a breeze, and once you have someone there there's no tangible reason to move to something else.
I don't mind the chat aspect. Instant chat is something common in communities, development or otherwise. I used to hang out on my share of dev IRC channels back when I was younger. I'd argue that instant chats like these are actually crucial for maintaining communities.
I mind Slack per se. I could understand non-technical communities going for it, but developers? Come on. Why choose a commercial walled garden that forces you to use a single, heavyweight and non-ergonomic interface? A product made by a startup, which can unpredictably go in any direction including disappearing overnight, if some big corporation opens their wallet widely enough?
I mind Slack per se. I could understand non-technical communities going for it, but developers? Come on. Why choose a commercial walled garden that forces you to use a single, heavyweight and non-ergonomic interface? A product made by a startup, which can unpredictably go in any direction including disappearing overnight, if some big corporation opens their wallet widely enough?
Because even developers appreciate the same UX ergonomics that our end-users users do. Did you think everyone uses Vim?
I don't really if all chat messages disappear. It's chat. It's ephemeral. No value to me beyond sentimental. And most people including myself think the UI is ergonomic, and far more featureful than any IRC client when nobody bothers to run their IRC clients on an always-on server.
The worst part of IRC is that everyone is offline the second they close their laptop or client when their question is. They won't be seeing your message. That only a few power users will bother to receive messages "while offline" is also a mark against IRC for the general public. Notice that developer /= IRC power user. Not even close.
I don't really if all chat messages disappear. It's chat. It's ephemeral. No value to me beyond sentimental. And most people including myself think the UI is ergonomic, and far more featureful than any IRC client when nobody bothers to run their IRC clients on an always-on server.
The worst part of IRC is that everyone is offline the second they close their laptop or client when their question is. They won't be seeing your message. That only a few power users will bother to receive messages "while offline" is also a mark against IRC for the general public. Notice that developer /= IRC power user. Not even close.
I disagree with you that Slack is an ergonomic interface. I'll give two examples off the top of my head:
1. New Threads sort with new items at the top.
This is opposite of everywhere else in the
app. And there is no indicator, e.g. the
date isn't displayed.
2. Try backspacing over an @ mention or two.
It is very unpredictable behavior.
I claimed it was ergonomic (at least more ergonomic than IRC since that was the comparison), not flawless.
And many of those ergonomic points come from features that IRC clients don't even have.
And many of those ergonomic points come from features that IRC clients don't even have.
And I'd rather use Vim.
Me too, but we're not the target demographic. In any case I think Matrix is the best bet for open communities right now - it has full slack integration anyway.
> Me too, but we're not the target demographic.
Well, that's a problem. How is it that tech savvy people created a tech industry that increasingly caters to everyone except the tech savvy people? It's getting really annoying. Operating systems are gradually losing features. A lot of software moved to the web, shedding functionality, and they evolve towards dumber and less functional forms over time. Smartphones are getting locked down and dumbed down. Hell, the only smartwatch company that made tools instead of toys went down, and I can't get a sensible smartwatch either. I don't like this trend.
Well, that's a problem. How is it that tech savvy people created a tech industry that increasingly caters to everyone except the tech savvy people? It's getting really annoying. Operating systems are gradually losing features. A lot of software moved to the web, shedding functionality, and they evolve towards dumber and less functional forms over time. Smartphones are getting locked down and dumbed down. Hell, the only smartwatch company that made tools instead of toys went down, and I can't get a sensible smartwatch either. I don't like this trend.
> at least more ergonomic than IRC since that was the comparison
IRC is just a protocol, it is up to the client to provide a nice interface.
IRC is just a protocol, it is up to the client to provide a nice interface.
> I don't really if all chat messages disappear. It's chat. It's ephemeral. No value to me beyond sentimental.
I don't think that's really the case here though. Developer communities chat about bugs, how they've solved them, future project plans, etc etc etc. It's not always just idle chat. It's a shame to lose that.
I don't think that's really the case here though. Developer communities chat about bugs, how they've solved them, future project plans, etc etc etc. It's not always just idle chat. It's a shame to lose that.
May be, but I also don't use any projects that have you searching chat logs (even if they exist) for future roadmap information, for example.
I think the point of log history search is fair but overrated.
It's easy to point out the feature, but I'm not convinced that regular chat search is part of anybody's centerpiece day-to-day bug-hunting strategy even on platforms with chat history.
Also, some things are better off on the forum. For example, Elm has a Slack and a forum. If you need to assume that all project discussion happens on Slack to find weaknesses in Slack, then I don't find those very compelling. It's just forum vs chatroom discussion and of course there are differences, just like how chat history doesn't make a chatroom competitive with a forum.
I know it looks like I'm going out of my way to "defend Slack" in the comments section here, but I think that Slack vs IRC arguments are the perfect example of how many developers are clueless about UX and things the end-user cares about. I just responded someone who couldn't think of a single reason someone would use Slack beyond "hipsterism" whatever that means (btw, I thought hipsters liked old stuff like vinyl records and Polaroids). It's something I see as a big problem in our field along with the stereotype of how developers cannot design products (not just visually) -- these arguments tends to validate those stereotypes.
I think the point of log history search is fair but overrated.
It's easy to point out the feature, but I'm not convinced that regular chat search is part of anybody's centerpiece day-to-day bug-hunting strategy even on platforms with chat history.
Also, some things are better off on the forum. For example, Elm has a Slack and a forum. If you need to assume that all project discussion happens on Slack to find weaknesses in Slack, then I don't find those very compelling. It's just forum vs chatroom discussion and of course there are differences, just like how chat history doesn't make a chatroom competitive with a forum.
I know it looks like I'm going out of my way to "defend Slack" in the comments section here, but I think that Slack vs IRC arguments are the perfect example of how many developers are clueless about UX and things the end-user cares about. I just responded someone who couldn't think of a single reason someone would use Slack beyond "hipsterism" whatever that means (btw, I thought hipsters liked old stuff like vinyl records and Polaroids). It's something I see as a big problem in our field along with the stereotype of how developers cannot design products (not just visually) -- these arguments tends to validate those stereotypes.
The problem is that many of these communities (and communities in general) are using systems like Slack for content that isn't ephemeral. Sure, use something like this to talk about the weather, what you're having for dinner or other things no one cares about in the long run.
But if you're talking about bugs, feature requests, future plans for the project, tech support... then use a proper forum or other more permanent solution, since otherwise tons of useful information just vanishes into the ether, especially with tools like Slack which have an actual message limit.
Still, they're not the only ones. Feels like almost everyone nowadays has forgotten about the value of having information stored for the long term. See the same thing with gaming communities on Discord too.
But if you're talking about bugs, feature requests, future plans for the project, tech support... then use a proper forum or other more permanent solution, since otherwise tons of useful information just vanishes into the ether, especially with tools like Slack which have an actual message limit.
Still, they're not the only ones. Feels like almost everyone nowadays has forgotten about the value of having information stored for the long term. See the same thing with gaming communities on Discord too.
They're unsearchable (with google), require an account just to read and have no seperation of discussion besides channels. I prefer forums.
Zulip has "topics" inside streams (kind of what they call channels).
Slack has "threads" which are meant to separate discussions, but they're not really convenient to use and are frequently unused.
I don't like it for a number of reasons:
* Exclusivity. Often they require some kind of signup before you can even read it. This isn't a big deal but I prefer a more open discussion.
* Lack of google visibility. Lots of good discussions will benefit the asker and a few people in the slack but no one in the future, searching for the same information.
* Lack of searching for the members. Once you get to 10k messages, you can't search the older ones. If you have a large slack, it doesn't take long to get there. And unless see company is willing to pony up thousands of dollars a month, those discussions are lost forever.
On the other hand, maybe three memory hole aspect of slack is actually a feature not a bug. Perhaps it lets folks speak more freely.
* Exclusivity. Often they require some kind of signup before you can even read it. This isn't a big deal but I prefer a more open discussion.
* Lack of google visibility. Lots of good discussions will benefit the asker and a few people in the slack but no one in the future, searching for the same information.
* Lack of searching for the members. Once you get to 10k messages, you can't search the older ones. If you have a large slack, it doesn't take long to get there. And unless see company is willing to pony up thousands of dollars a month, those discussions are lost forever.
On the other hand, maybe three memory hole aspect of slack is actually a feature not a bug. Perhaps it lets folks speak more freely.
> * Lack of google visibility. Lots of good discussions will benefit the asker and a few people in the slack but no one in the future, searching for the same information.
> Lack of searching for the members. Once you get to 10k messages, you can't search the older ones. If you have a large slack, it doesn't take long to get there. And unless see company is willing to pony up thousands of dollars a month, those discussions are lost forever.
This is the default state on the old real-time communication medium, IRC. Communities can solve the problem on Slack the same was as on IRC, using accounts controlled by bots who log channel messages. If the bot then puts the logs somewhere Google can find, you have a record that can be Googled. This only happens for the public if somebody cares.
> Lack of searching for the members. Once you get to 10k messages, you can't search the older ones. If you have a large slack, it doesn't take long to get there. And unless see company is willing to pony up thousands of dollars a month, those discussions are lost forever.
This is the default state on the old real-time communication medium, IRC. Communities can solve the problem on Slack the same was as on IRC, using accounts controlled by bots who log channel messages. If the bot then puts the logs somewhere Google can find, you have a record that can be Googled. This only happens for the public if somebody cares.
You actually can't do this with slack and be compliant with their TOS (https://slack.com/terms-of-service/api):
"Functionality. You may not use the Slack API to replicate or compete with core products or services offered by Slack. You acknowledge and agree that Slack has or may in the future offer products or services that are similar to your Application, and nothing will prevent Slack from doing so;"
So any communities doing this can get their community shut down by slack at any time.
"Functionality. You may not use the Slack API to replicate or compete with core products or services offered by Slack. You acknowledge and agree that Slack has or may in the future offer products or services that are similar to your Application, and nothing will prevent Slack from doing so;"
So any communities doing this can get their community shut down by slack at any time.
> Lack of google visibility. Lots of good discussions will benefit the asker and a few people in the slack but no one in the future, searching for the same information.
It's true, but there is also a lot of information that is no more relevant, yet comes first in search. With IRC or Slack, you may lose some of the benefits of archived discussion but you get fresh information .
Plus, most of the conversation on these channels is chat. By nature, it is ephemeral and should stay that way.
It's true, but there is also a lot of information that is no more relevant, yet comes first in search. With IRC or Slack, you may lose some of the benefits of archived discussion but you get fresh information .
Plus, most of the conversation on these channels is chat. By nature, it is ephemeral and should stay that way.
This is a well reasoned post, so my first reaction is to agree with you. But, then I remember two things. First, I largely learned to program because of some (extremely patient) people on IRC. IRC is similar to Slack in that it theoretically silos away questions and answers and prevents future discoverability. And second, despite all these years of conversations that were held on IRC, I can still find answers to any question imaginable on Google.
In retrospect, I think that Slack (or IRC) might actually be a great way to disseminate information from developers to highly technical people. And, I think that many of these first generation learners blog about what they learned or go to answer questions on other services (ie - StackOverflow).
But, I'm a sample of one and have absolutely no proof of any of this...:)
In retrospect, I think that Slack (or IRC) might actually be a great way to disseminate information from developers to highly technical people. And, I think that many of these first generation learners blog about what they learned or go to answer questions on other services (ie - StackOverflow).
But, I'm a sample of one and have absolutely no proof of any of this...:)
I don't like this trend either. What I particularly don't like is that to be signed in into multiple Slack communities, I need to add them to the Slack desktop app. And the more apps I have, the worse the desktop app seems to perform.
I wish the developer communities would realize that IRC has been around for years and performs much much better than Slack.
I wish the developer communities would realize that IRC has been around for years and performs much much better than Slack.
Old IRC veteran here, spent lots of time on #OSWD and loved it. Having said that, we have IRC at our hackerspace I a despise it because of I'm not connected all the time and miss out on important org business. For a few months we plugged matrix.org into the irc and it is a blessing.
Discord seems to be a more elegant solution than Slack tbh, and I happen to be on several developer servers. The web app/desktop app/mobile app all function brilliantly.
The issue I have with Discord is the lack of threads. When you're helping multiple people at once threads can help distinguish who you're talking to. Or when you have multiple conversations happening at once it stops things getting confusing.
wholeheartedly agree with this. The counter on the top an be annoying as it just aggregates all private chats.
Agree. One huge plus over Slack is that you don’t need a separate account for each community. And joining can be easily done via just clicking a link.
I feel like slack is better for work. But for almost everything else, I just want to check out a channel without the overhead of creating an account.
Could you suggest some ?
http://unrealslackers.org/
https://godotengine.org/community
Both game engine examples but super helpful developer communities none the less.
Both game engine examples but super helpful developer communities none the less.
I'm not necessarily vouching for Slack here, but I routinely have 2 Slack tabs open in Chrome for 2 different communities.
The desktop app is unusably slow on my machine.
The desktop app is unusably slow on my machine.
You have to ask yourself why someone would use Slack despite IRC instead of assuming they're ignorant.
Then you'll see that there's also the question of "why IRC when we can just use Slack?" If you can't think of any answers to that, then you're not really equipped to eval the trade-offs.
Then you'll see that there's also the question of "why IRC when we can just use Slack?" If you can't think of any answers to that, then you're not really equipped to eval the trade-offs.
Hipsterism? I do not think of any other reason to use something that for all practical uses is the same as IRC but instead of relying on an open protocol that would allow for multiple clients and servers, it uses its own proprietary lock-in tech that forces people to use a slow resource draining client.
(ok, i can think of one: "funny" emoticons. But i file that under hipsterism and if you really wanted, some IRC clients allows emoticons, but others might frown on your use of :sadbatman: :-P)
(ok, i can think of one: "funny" emoticons. But i file that under hipsterism and if you really wanted, some IRC clients allows emoticons, but others might frown on your use of :sadbatman: :-P)
That you can only think of something negative of people who use something says more about you. Inability to understand the decisions of others isn't going to serve you well in life.
None of the positives for IRC that you mention facilitate the reason people actually use chat platforms: having conversations and forming communities.
Do you think people use IRC because it has an open protocol or because they want to chat?
The next step for you is to ask yourself what features Slack might have that does facilitate chat and community-building. Since you can only think of "funny faces", it sounds like you should actually download it and try it first.
And you'll soon be on your way to seeing other people as rational individuals with an appetite for different trade-offs than you instead of a bunch of idiots that just don't see the light.
None of the positives for IRC that you mention facilitate the reason people actually use chat platforms: having conversations and forming communities.
Do you think people use IRC because it has an open protocol or because they want to chat?
The next step for you is to ask yourself what features Slack might have that does facilitate chat and community-building. Since you can only think of "funny faces", it sounds like you should actually download it and try it first.
And you'll soon be on your way to seeing other people as rational individuals with an appetite for different trade-offs than you instead of a bunch of idiots that just don't see the light.
I didn't really mention positives for IRC, i mentioned negatives for Slack.
> Do you think people use IRC because it has an open protocol or because they want to chat?
Most of the people who use IRC or Slack or Discord or HipChat or Skype or any other similar tech, do it because they want to chat. However not all uses are the same - creating a new chat room and entering the chat room are both uses, but the former means that you are in a position to decide what the people who will perform the latter will need to do. The people who will enter the chat room will not really be in a position to make much of a choice beyond entering the room/community or not, so their reasoning behind that choice is irrelevant when it comes to the selection of the technology for the chat room.
The people who will create the chat room, however, are those who will make those choices for everyone that follows in that room/community and it is to those people that i am referring to with "I do not think of any other reason to use something that for all practical uses is the same as IRC" - because there is really no reason to not use IRC and minor features that Slack or HipChat or Discord to some extent (Discord provides audio chat which some communities might prefer, although TBH personally i highly dislike it and any "server" - lol - i've seen that uses audio channels has them almost always empty) are not worth the restrictions these services impose on the other members of the community you are trying to create.
> Do you think people use IRC because it has an open protocol or because they want to chat?
Most of the people who use IRC or Slack or Discord or HipChat or Skype or any other similar tech, do it because they want to chat. However not all uses are the same - creating a new chat room and entering the chat room are both uses, but the former means that you are in a position to decide what the people who will perform the latter will need to do. The people who will enter the chat room will not really be in a position to make much of a choice beyond entering the room/community or not, so their reasoning behind that choice is irrelevant when it comes to the selection of the technology for the chat room.
The people who will create the chat room, however, are those who will make those choices for everyone that follows in that room/community and it is to those people that i am referring to with "I do not think of any other reason to use something that for all practical uses is the same as IRC" - because there is really no reason to not use IRC and minor features that Slack or HipChat or Discord to some extent (Discord provides audio chat which some communities might prefer, although TBH personally i highly dislike it and any "server" - lol - i've seen that uses audio channels has them almost always empty) are not worth the restrictions these services impose on the other members of the community you are trying to create.
Not a fan. Annoying to access, limited history, ...
Can be improved with having external logs and/or a strong culture of moving things to external documentation, you can set up open gateways for joining, ..., but few Slack-based communities bother.
Can be improved with having external logs and/or a strong culture of moving things to external documentation, you can set up open gateways for joining, ..., but few Slack-based communities bother.
Over the years I've seen projects using stackoverflow to answer dev/user questions and just recently I started using http://stimulusjs.org/ which runs a discourse installation for their users. Which I like a lot because it discourse is fixing a lot of the problems stackoverflow has while not being a chaotic chat like slack.
I like my information well-ordered, grouped, focused and easy to search. Slack is a waterfall I just can't stand. (plus the emojis, am I too old for those?)
I like my information well-ordered, grouped, focused and easy to search. Slack is a waterfall I just can't stand. (plus the emojis, am I too old for those?)
If we're talking about an open-source project dev community, I honestly think there are better tools out there these days.
There are two main problems I have with Slack communities: the message limit, and having to create yet another account. Being able to search for a question that may have already been asked is great, and the need for more accounts is a bit of a turnoff too.
Gitter was specifically built with open-source projects in mind, which is great. However, once a project becomes large enough, having a single channel is probably not conducive to productivity.
Lately I've started seeing open-source communities use Discord, which seems rather interesting.
Of course, there are also the projects out there that use Matrix and have IRC and Gitter bridges.
Having said all this, I'm also a part of some non-project-based Slack dev communities. I can definitely see the appeal to these; a lot of people already use Slack for work, after all.
There are two main problems I have with Slack communities: the message limit, and having to create yet another account. Being able to search for a question that may have already been asked is great, and the need for more accounts is a bit of a turnoff too.
Gitter was specifically built with open-source projects in mind, which is great. However, once a project becomes large enough, having a single channel is probably not conducive to productivity.
Lately I've started seeing open-source communities use Discord, which seems rather interesting.
Of course, there are also the projects out there that use Matrix and have IRC and Gitter bridges.
Having said all this, I'm also a part of some non-project-based Slack dev communities. I can definitely see the appeal to these; a lot of people already use Slack for work, after all.
Gitter’s search is also terrible and barely existent. I think this is to do with the way they store logs after a month.
I suggest Zulip as an alternative. Two main advantages:
- free & open source.
- threads are google-able and linkable.
- free & open source.
- threads are google-able and linkable.
I see what you're saying, and I agree with all your points, but there are positive points as well:
1) When you need low-latency help, i.e. where you need to have a conversation about your problem, a real-time communications medium is ideal.
2) They do tend to lean towards becoming communities, and communities are very good at driving engagement within that community. I've joined a few Slack communities and become a contributing member, whereas I experimented with early Stack Overflow and haven't really engaged with it since.
Honestly, I think they tend to lead to stronger communities, since you have to join and participate even a bit to get your answer out of it. With GG/SO, you can just pop in, read your bit, and move on, having never contributed.
1) When you need low-latency help, i.e. where you need to have a conversation about your problem, a real-time communications medium is ideal.
2) They do tend to lean towards becoming communities, and communities are very good at driving engagement within that community. I've joined a few Slack communities and become a contributing member, whereas I experimented with early Stack Overflow and haven't really engaged with it since.
Honestly, I think they tend to lead to stronger communities, since you have to join and participate even a bit to get your answer out of it. With GG/SO, you can just pop in, read your bit, and move on, having never contributed.
I've become a regular on Symfony's (PHP framework). It works really great for creating a sense of community. Slack is great to talk with each others and split concerns between channels. The thread feature is great at keeping the main channels from getting clogged.
Now the main issue is that those Slack workspace are always on free tier. The only other options would be to charge the users as it's a fixed price per users and paying $8/users/month is impossible for open source projects.
Since those are on the free tier, message history is lost. You cannot leverage Slack's great search engine and community support gets lost. On a regular forum, you could search for previous questions. On Slack, you cannot.
Now the main issue is that those Slack workspace are always on free tier. The only other options would be to charge the users as it's a fixed price per users and paying $8/users/month is impossible for open source projects.
Since those are on the free tier, message history is lost. You cannot leverage Slack's great search engine and community support gets lost. On a regular forum, you could search for previous questions. On Slack, you cannot.
I would rather have the projects advocate IRC with some nice frontend, I get there are some benefits of slack for developers, but this is thin ice - unless the projects are prepared to pay for channels that have thousands of users.
They are great because they create actual communities.
Chat is ephemeral. If you have a question that's not on StackOverflow, then you can just ask people in chat. It's even better for deeper questions because you can have a conversation.
Not every social vessel we have in the world needs to become an archived knowledgebase. And one of the reasons StackOverflow exists is because it's so hard to mine Q&A from even more static mediums like forums much less chatrooms.
Chat is ephemeral. If you have a question that's not on StackOverflow, then you can just ask people in chat. It's even better for deeper questions because you can have a conversation.
Not every social vessel we have in the world needs to become an archived knowledgebase. And one of the reasons StackOverflow exists is because it's so hard to mine Q&A from even more static mediums like forums much less chatrooms.
I love that Slack exists. I don't see any need to use it myself. It provides a great honeypot for the Eternal September influx. IRC is (to steal Metacity's slogan) like Cheerios.
(Yes, I used Slack for a while, at a company I worked for. I found it technically unimpressive, and the UI seems to be designed primarily to encourage every channel to descend into emoji and memes, and to maximize distraction.)
I find the lack of logging/search on IRC to be a feature. I think people are more open in a community when they know they're not going to be hyper-analyzed by strangers on the internet in the distant future. There do exist IRC loggers, but I think most of the channels I frequent don't allow them.
(Yes, I used Slack for a while, at a company I worked for. I found it technically unimpressive, and the UI seems to be designed primarily to encourage every channel to descend into emoji and memes, and to maximize distraction.)
I find the lack of logging/search on IRC to be a feature. I think people are more open in a community when they know they're not going to be hyper-analyzed by strangers on the internet in the distant future. There do exist IRC loggers, but I think most of the channels I frequent don't allow them.
Overall, they are good simply because you do often get quick real-time help, like Irc but with more people.
I find spectrum.chat working better for communities when compared to slack. Somehow slack adds too much noise to your "work communication"
And I hate when people tag the whole channel for some silly reasons(most communities disable this option...but still)
And I hate when people tag the whole channel for some silly reasons(most communities disable this option...but still)
[deleted]
I agree with all the other negative comments here plus one more - Slack just isn't very good software, it frequently bugs out or outright crashes and is rediculously slow.
misc thoughts -- if the service is free, then you are the product...
Commercial companies can change their terms at will, and are long-term motivated towards vendor lock-in ...
FOSS producers need FOSS IRC channels..
and lastly, crowds move by both fashion and fiat. Efforts may not be immediately returned, but over the longer term this can change quite a bit.
I agree. the information they're sharing would better serve those communities by being public.
Its a short-sighted solution.
Its a short-sighted solution.
I think steering questions to a chat is a terrible idea. There is no collective learning anymore.
It sucks. Bring back IRC now!
IRC never went away and is alive and well, and still both useful and fun.
I keep hearing that and then I go to an irc room and ask a question and sit... and sit some more... I think I’m at 5 times in a row now that no one even answered. I am done wasting my time there. Irc might not be totally dead but despite all the denial it’s definitely on its way out. And good riddance.
Was this on freenode? What channel?
[deleted](3)
[deleted]
https://spectrum.chat tries to solve the problem of giant Slack communities. It gained a lot of popularity in the last year + it's open source, if that is something you care about.
My gut reaction to this is a negative one, where I feel like the siloing of developer releated questions and answers is against the nature of the web, and more importantly detremental to the community itself, as it prevents discovery of previous discussions in forums, Google Groups, Stackoverflow etc.
How do you feel about these?