|
|
|
|
|
by hot_gril
1170 days ago
|
|
I worked on a customized ejabberd at a company for years, drinking all the XMPP kool-aid and becoming very familiar with XML along the way. Slowly we all began to realize how bad XML was. We eventually put our custom extensions' data into JSON just embedded inside the XML. Says a lot that such a hack was actually an improvement. The other two premier XML use cases I can think of are 1. RSS: Last time I did this, ironically I built the payload with a JSON-API'd lib that deals with the XML drama for me. Worked fine. 2. Configs. Rarely are these done in XML anymore. Human readability matters for configs. But there are also better options than JSON for this. |
|