Ah yes, Matrix support added before Exchange support!
Matrix support is probably a ton easier.
Besides, matrix is designed to be implemented by multiple parties. Exchange isn’t. In fact, exchange is almost certainly the opposite.
Believe there are libraries available as well.
I don't blame the devs, Exchange is a proprietary standard so you can't expect it to work well. It's like the reverse-engineered drivers for hardware the manufacturer doesn't bother to write Linux support or sufficient documentation for: it doesn't work great, but that's despite the devs' best effort, not because of it.
it has been working beautifully for me in the past 6-7 years
including calendar and contacts
> the manufacturer doesn't bother to write Linux support or sufficient documentation for
you mean documentation, like this?
https://docs.microsoft.com/en-us/exchange/client-developer/w...
Microsoft has many flaws, but not writing documentation it's not usually one of them.
There are at least two, based on EWS (Exchange Web Services):
- evolution-ews (Gnome)
- akonadi-ews (KDE)
A lot of companies seem to have switched to Office365 which is not the same thing and most of the one I have worked with block third-party clients in their security policies.
As cloud costs ratchet up and the weaknesses become more apparent, I suspect you'll see orgs start migrating back away from the cloud.