5 ms·

And XMPP has consistently been behind on innovation. I used IRC and Jabber for a really long time. I don't know how long I was waiting for basic audio and video

And XMPP has consistently been behind on innovation. I used IRC and Jabber for a really long time. I don't know how long I was waiting for basic audio and video chat in XMPP, which is now a standard thing in almost all proprietary communication systems. People have been wanting those features for a very long time and they migrated away from the open systems because they were consistently behind on features. I don't understand why open seems to immediately mean better and proprietary is bad. I'm all for an open system if the benefit is clear, but it often makes no difference and ultimately comes down to how the project/software is managed. There are a lot of "open" software products that are controlled by a few and thus, not very open.

viraptor 11y ago
I don't think what you write makes sense really. Sure, XMPP has been behind on innovation. Companies using it had four choices: wait for X, implement solution in XMPP and publish it, implement solution in XMPP silently, reimplement everything including X. Well, we ended up with tens of platforms with X, so obviously companies went with one of the latter two solutions. We know a few of the companies did continue with XMPP and modified ejabberd, so they definitely did XMPP implementation of video for example. Yet, they decided not to publish anything, so globally we're stuck in the same place again. Similar thing happened to HTML with ages of stagnation. Now we finally standardise what's implemented instead of implementing what's standardised. I don't see how XMPP itself is an issue. Don't like that they're slow? Use your own extension and publish it. Either everyone will use the same solution, or you'll learn why it sucks.
lmm 11y ago
Never mind audio/video, the group chat UX for Jabber still sucks, as does the experience when logging in from multiple devices (something you'd think tech people would have caught onto early).

viraptor 11y ago

I don't think what you write makes sense really. Sure, XMPP has been behind on innovation. Companies using it had four choices: wait for X, implement solution in XMPP and publish it, implement solution in XMPP silently, reimplement everything including X. Well, we ended up with tens of platforms with X, so obviously companies went with one of the latter two solutions. We know a few of the companies did continue with XMPP and modified ejabberd, so they definitely did XMPP implementation of video for example. Yet, they decided not to publish anything, so globally we're stuck in the same place again. Similar thing happened to HTML with ages of stagnation. Now we finally standardise what's implemented instead of implementing what's standardised. I don't see how XMPP itself is an issue. Don't like that they're slow? Use your own extension and publish it. Either everyone will use the same solution, or you'll learn why it sucks.

lmm 11y ago

Never mind audio/video, the group chat UX for Jabber still sucks, as does the experience when logging in from multiple devices (something you'd think tech people would have caught onto early).