3 ms·
This is true for people who write applications. It is not true for people who would like to write servers and XMPP libraries that are somewhat efficient. XMPP
by bborud 10y ago
This is true for people who write applications. It is not true for people who would like to write servers and XMPP libraries that are somewhat efficient.
XMPP also isn't usable for many new IoT applications where it should have had its opportunity to shine, but where there just isn't enough memory to deal with the ridiculous bulk.
But I do get that most developers don't really try all that hard. I mean, look at the resource usage of Slack. It is an application that does _nothing_ that requires CPU, yet it gobbles it up. It tells you something about the kinds of people that write chat applications today. Not exactly the sharpest tools in the shed.
- upofadown 10y ago>...the ridiculous bulk. Well presumably this hypothetical IoT application would have to support TCP/IP. Against that, a few hundred bytes of state table for the limited subset of XML required for basic XMPP would count for much.
- bborud 10y agoYou presume. I write code that has to deal with it. That's the difference.