3 ms·

My “why not Matrix” is that it’s hard to build a good client for it and hence there are incredibly few (on some days I’d argue none). To the project’s credit:

My “why not Matrix” is that it’s hard to build a good client for it and hence there are incredibly few (on some days I’d argue none). To the project’s credit: A lot of work has gone into supporting better UX (QR code sign in, sliding sync) and the Rust library is also apparently pretty good. Yet, somehow, there still hasn’t been an explosion of clients. IMO it’s because the protocol carries too much cruft and the standardization process (including vendoring) makes it hard to use new features when not using the official libraries, which are a) under-documented and b) only available from Rust, Swift and Android.

K0IN 1y ago
+1 I also want to add, I'm using beeper and there new app is fantastic but the old desktop app (and current webapp) are based on element. Which for me had the worst experience possible, startup times way beyond 1 minute, the webapp just runs into a chrome oom when I keep it open for longer than 1 hour and also the user interface is super unresponsive and laggy. I tried element (without beeper) and had the same issues, that's why I never got into matrix.
BrenBarn 1y ago
Yeah, agree. If you look at their list of SDKs things look great, but in my experience once you actually look into them, you find many are missing important features. The protocol is still getting changes that are, if not exactly backwards-incompatible, definitely backwards-inconvenient. There's also a catch-22 in that, due to this problem, usage is heavily skewed towards Element, which means that Element's behavior becomes a de facto spec.