No problem against it but please don't migrate to discord, migrate to Matrix. My plea has nothing to do with product quality but that with Matrix I can access other bridged people. But discord and pals not so much.
Wasting 8gb ram on slack, already on gitter, teams, google meet and I am not even a people's person others have more platforms active in parallel.
This is why I don't support any platform that does not also use an interoperable protocol. This includes Signal which won't let 3rd party clients connect to its servers. Protocol is a foundational element of communication. If you are designing a communication system that others that are strangers to your system can't talk to your users because you don't have a protocol, your system isolates users and is hostile to its very purpose:communication.
I mean really, I rant here a bit but have all these smart people never heard of adversarial compatibility?
For Matrix, I really wish they didn't associate with their flagship client, others who build clients have to also compete with the protocol authors, this should be a lesson to future communications systems designers.
I'm interested in matrix, how can I learn more and can you choose providers or clients, any recommendations?
For hosting, I believe the flagship host is Element Matrix Services [2]. It's made by the same organization that leads development (it is all FOSS) of Element and the reference server Synapse.
You can also self-host. Synapse is pretty slow and memory-hungry (it's written in Python), but for a small group it still fits pretty comfortably on a $5 DigitalOcean VPS. That's what I'm doing. It took less than an afternoon to set up (`apt install synapse` and then setting some config, mainly—there are a bunch of good guides online) and has been happily running ever since. Matrix is federated, so as long as you set up federation properly, you can seamlessly message anyone on any federated Matrix server. (Federation is opt-in.)
There's also Dendrite and Conduit, Matrix servers written in Go and Rust respectively, which are much leaner and faster. Both are still in beta and missing some features, but are definitely usable.
If you want to mess around with bots, I've had a lot of fun with both the Matrix Rust SDK [3] and JavaScript bot SDK [4]. Both are quite easy to get started with, and as of a few months ago both support E2EE pretty painlessly too (not totally pain-free though lol), which is cool.
Overall, the ecosystem is still maturing imo, but I've been using self-hosted Synapse and Element "in production"—it's me and my girlfriend's primary method of communication—for over a year now with only some minor UX hiccups (mostly issues decrypting E2EE messages in Element). I definitely encourage giving it a shot as long as you're willing to tolerate a few remaining growing pains.
[1]: https://element.io/get-started
[2]: https://element.io/matrix-services