From what I see it's a product team decision to have something like that. Kotlin and RubyMine teams decided they want it, other teams - not [yet]
👌 1
p
poohbar
02/22/2018, 3:51 PM
I don't care about the teams that much. I understand why they would not want to participate but having one official JetBrains slack would allow users to quickly help each other with quirks related to the IDEs. I see no downside.
c
Czar
02/22/2018, 4:11 PM
One downside is the answers provided being ephemeral, whilst on resources like stackexchange network they stay and are easily searchable.
Another is moderation overhead. Look at this slack, we already have problems here and it's only kotlin community, imagine what it will be like for the whole JetBrains technology stack.
Third is 10k messages limit, for Kt community it is mostly ok, but for a larger one conversations could disappear before they are actually concluded and that would probably happen a lot, seeing how here some of the questions/situations are resolved after several days.
Czar
02/22/2018, 4:13 PM
Most of JetBrains related problems are easily googleable, for stuff that isn't, there's forum, youtrack and stackexchange, I'd say that's enough. Sure, slack would be a nice bonus, but it's not like it is needed.
Anyways, you asked about downsides, that's my take on it 🙂