We have a WCF service with an odd configuration and nobody has been able to integrate with it that didn’t use Microsoft tools. It’s definitely not XML’s fault.

(That service has been replaced with a REST API now)

[–] RonSijm 5 points 2 months ago* (last edited 2 months ago)

It’s more the fault of the implementation and documentation.

Yea sure. Though it's slightly XMLs fault for allowing that kinda implementations. Every random thing is in it's own obscure namespace with 20 levels of nested objects in different namespaces, and if you get anything wrong it barely explains what's wrong, and just refuses to work.

It's mostly WCFs fault. I just automatically associate XML with nightmare flashbacks of implementing WCF stuff