Live data from Hacker News

21 XMPP use-cases and the best ways to achieve them

erlang-solutions.com

21–23 of 23 posts

Re: 21 XMPP use-cases and the best ways to achieve them

#21
post #4
post #3

Earlier quoted context omitted.

Gajim [1] implements a lot of modern XEPs (directly or through easy to install plugins), including OMEMO. I don't know how well it works on non Linux systems (they provide Windows binaries at least). [1] https://gajim.org/

it works. doesn't feel very native, but then neither do a lot of the big names in chat right now

It is worse, actually, because it uses GTK, and is only available on Linux and Windows (not macOS, although there have been attempts).

Most of the "big names" who provide modern and contemporary desktop IM apps deliver on the 3 platforms (Linux, macOS, and Windows), and use mostly web "technologies" (sometimes "pure browser", and sometimes with electron-like desktop "packaging")... so as a consequence, it is very native, indeed, but it is a generally consistent and continuous UX (user experience) between mobile/tablet and desktop/laptop.

Re: 21 XMPP use-cases and the best ways to achieve them

#22
post #20

Earlier quoted context omitted.

MongooseIM (and ejabberd) are too big and complex to allow full hot code reloading. Moreover this feature is quite rarely used in any Erlang software.

I'm not sure how you've measured how often hot code reloading is used? I use it for almost all of my production pushes. However, I agree that it's generally hard to use it for third party software; upgrades would either become cumbersome because you have to follow the same piecewise upgrade process the developer followed, or the developer would have to do a lot of extra work to ensure upgrades between releases were s…

I could point to this: https://stackoverflow.com/questions/31080970/erlang-hot-code...
Post reply on HN