tfar

https://flutter.dev/ and https://fastlane.tools/ as well.

Certainly not transparent file system compression. Can save developers couple 10 GBs but hey (source code, binaries, debug symbols, all compress nicely).

One example is shown in this 2017 FOSDEM talk: https://archive.fosdem.org/2017/schedule/event/xmpp_iot/

Is there a way to cache build results for follow up builds? So the next build only needs to rebuild the files that changed?

"CF doesn't even host them, they just protect their sites from DDoS and DNS."

The #1 excuse people use. They do more than just DNS, they deliver the actual data, that would have been delivered by the original host, to visitors. So I'd consider them hosting an automatically updated mirror, and as bad as the original host.

  "HR serves to protect the company"

Why do you need a extension for that? Wouldn't it be enough for the client app to register a custom URL scheme handler and their website using that custom URL scheme to open the client?

That is not a sign of the quality of the language though. It is more a sign of how much money went into making a poor quality language perform well. Compare the speed of JS JIT VMs to Lua JIT VMs considering the investment respectively for example.

Well, to be pendantic, it's not the Signal protocol. It's a Signal-like protocol, Olm, brought to XMPP/Jabber.

Also see this for Asterix, Opos, VP8 and patents: http://lists.digium.com/pipermail/asterisk-dev/2013-May/0604...

I would not be surprised if one could write a ZFS implementation optimized for more constrained devices. If you already know you are going to a have flash storage you can probably ditch some of the N layers of cache you see in common ZFS implementations. Not that ZFS is a one size fits all, but the file systems specification could be implemented in more than one way.

But XMPP gives you another freedom. The freedom to choose your user experience. User experience describes the way we use something.

I don't think users care about the freedom to choose the UX. They just want a good UX and that's it.

Slack in turn fails to provide a decent mobile experience.

According the ratings of app stores, users are pretty happy with them.

PGP has been around in the XMPP community for several years but is currently being reworked into a more modern extension called XEP-0374: OpenPGP for XMPP Instant Messaging that promises to make the onboarding easier for novice users.

I don't get how something OpenPGP will make onboarding any easier for XMPP. New XMPP users who might have an automatically generated account somewhere, still start with an empty contact list. Onboarding is definitely the key issue for mobile XMPP.

There basically is. Linux per se is just not a desktop OS, like Windows or OS X. Ubuntu has a standard UI, Debian's default install has a standard UI, Kubuntu has a standard UI, and so on.

It helps okay. I recently used it to slowly and mostly automatically introduce more and more C++11 across a bigger code base. For example it does a great job introducing nullptr [0] and an okay job turning classic for loops into range based for loops [1] where possible.

[0] https://github.com/swift/swift/commit/eddd92ed76ae68cb1e2026... [1] https://github.com/swift/swift/commit/3c560e31b0f168da917e8d...

You could also have clients and servers implement http://xmpp.org/extensions/xep-0357.html .