It's really a shame when people can't look past the surface, and just emit vague subjective rebukes like this. XML may not be fashionable today, but really it poses no technical issues compared to the kinds of actual hard technical issues involved in making an open and decentralized IM network that XMPP has been solving for 15 years.
Using someone else's wrapper library is like (insert sufficiently disgusting analogy for doing something with a pile of excretia).
At the end of the day, the underlying product is still an overwrought, overly verbose mess, and the wrappers only serve to hide that. And following the law that all abstractions are leaky, you're going to have to touch it eventually.
A better replacement would be IRC. It serves almost all of the XMPP use cases with no extension, and i'd wager all of them with the right daemon and right plugins.
Comments
- https://github.com/otalk/stanza.io
- https://github.com/xmpp-ftw/xmpp-ftw
It's really a shame when people can't look past the surface, and just emit vague subjective rebukes like this. XML may not be fashionable today, but really it poses no technical issues compared to the kinds of actual hard technical issues involved in making an open and decentralized IM network that XMPP has been solving for 15 years.
Using someone else's wrapper library is like (insert sufficiently disgusting analogy for doing something with a pile of excretia).
At the end of the day, the underlying product is still an overwrought, overly verbose mess, and the wrappers only serve to hide that. And following the law that all abstractions are leaky, you're going to have to touch it eventually.
A better replacement would be IRC. It serves almost all of the XMPP use cases with no extension, and i'd wager all of them with the right daemon and right plugins.