undefined | Better HN

0 pointsabustamam6d ago0 comments

> useful for creating islands of sanity/enforcement in a codebase

Thanks for the insight! Is this what JSDoc/Swagger is now used for?

> I can't quite picture this: how does one parse XML to JSON?

I'm not sure actually. I haven't personally seen the code, I just hear my coworkers always lambasting that API provider for their usage of XML. Maybe it's just their lack of documentation that sucks, but it's become a running joke whenever we get a new partner that the team integrating it jokes that their API is XML.

0 comments

jeroenhd6d ago

> I just hear my coworkers always lambasting that API provider for their usage of XML

I hear this too, but often when I ask why people say things like that, it's either because XML is "outdated" or because they don't like it.

It's like programs written in C or C++: very few large projects chose those languages nowadays, often for good reasons, so the projects written in those languages are usually 10 to 20 years old. Age comes with a lot of legacy cruft and obscure behaviour, but that's not the fault of those languages per se. Or for people blasting banks for using COBOL, even though COBOL is a perfectly fine high-performance language for the niches bank mainframes serve.

j / k navigate · click thread line to collapse

0 comments

jeroenhd6d ago

> I just hear my coworkers always lambasting that API provider for their usage of XML

I hear this too, but often when I ask why people say things like that, it's either because XML is "outdated" or because they don't like it.

j / k navigate · click thread line to collapse