this post was submitted on 09 Sep 2024
417 points (96.2% liked)

Programmer Humor

19623 readers
1902 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] RonSijm@programming.dev 13 points 2 months ago (1 children)

Uh-huh... ever tried to integrate with a poorly implement WCF service? Like communication from a Java service to a dotnet service through a WSDL?

I'll take a json API over XML any day

[–] nogooduser@lemmy.world 10 points 2 months ago (1 children)

I’m not sure that’s the fault of XML though.

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

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@programming.dev 6 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