I'm also strongly of the opinion that tying core business functionality and information transfer to a third-party chat application is a massive footgun, and other than the fact that I use it out of business needs and not just for voice, I think s/Discord/Slack/g applies. I've both heard Discord described as "Slack for hobbies" and Slack as "Discord for the employed" (although obviously it's not a perfect distinction and I've seen e.g. Netrunner groups on Slack and e.g. some startups communicating through Discord).
That said, the number of teams and departments I have either encountered or heard about from engineering friends elsewhere whose primary - and sometimes only maintained - deployment interface is a Slack command clearly means that I'm the dumb one for trying to work the UNIX philosophy into most of my life's tools and nobody else is blinking twice about vendor lockin and memoizing solutions in a chat application. I just try and take any question/answer that was sufficiently obscure or anything asked more than once and shove it in an "OAQs" ("occasionally asked questions") on Confluence or whatever the knowledgebase application du jour is, but it still feels like teardrops against the ocean sometimes.