I have the same question. The documentation does a good job presenting the language, but not the motive or sweet spot use case.
It's as if the new generation of developers doesn't realize the difference between transient conversations (which is what happens on Discord/Slack) and creating knowledge (which needs to be persistent and searchable, neither of which is afforded by aforementioned chat services).
This applies to communities in general (on-line and off-line). Knowledge needs to be captured outside of the minds of select participants. It's e.g. why, in our local Hackerspace, I always insisted on the rule that anything said on IRC (or later, Telegram) is non-binding - the only things that matter are ones decided on the mailing group or documented on the wiki. To do otherwise is to force out everyone who can't keep pace with the common chat.
But regardless, my experience is that once languages reach a critical mass they do get real documentation in a more browsable format. And I think Discord is a totally valid temporary solution for documentation, and a totally valid replacement for discussion groups.
I was simply stating that the Discord channel exists and that the answer to the question can be found there. Sorry someone took personal offensive to that.
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.