If they had of just set up XMPP as a messaging system we would of never heard of it. It would of been an entirely routine thing to do.
Synapse feels like a bloated monster that I'm afraid to touch in case it goes bang and I can't recover.
Prosody felt like a simple light weight service that I could easily recover no matter how much I broke it.
The consumer-facing client ecosystem for XMPP has indeed seen less rapid development than Matrix (the latter probably benefits from a more cohesive approach), but the server ecosystem for XMPP is very mature, and servers such as Ejabberd are known to scale to hundreds of thousands of connections on a single, modest host[3]. Obviously, that's only one part of the puzzle, hence why Matrix was chosen here.
Still, it'd be interesting to see how the two evolve and compare down the line.
[0]: https://www.erlang-solutions.com/case-studies/pando-health-c... [1]: https://medium.com/miquido/successful-migration-to-a-custom-... [2]: https://twitter.com/iNPUTmice/status/1203611711967813633 [3]: https://www.process-one.net/blog/ejabberd-nintendo-switch-np...
(It's true that many contributions to Matrix come from Element, though, the VC-funded for-profit founded by the original Matrix team in order to pay for us to keep the lights on and keep working on Matrix. Just as VC-funded Jabber Inc contributed massively to XMPP, back in the day).
Is one of the best ways to support Matrix and grow the influence to hire Element’s team as consultants to build custom implementations and use cases?