←back to thread

392 points _kush | 1 comments | | HN request time: 0.421s | source
Show context
CiaranMcNulty ◴[] No.44394259[source]
It's sad how the bloat of '00s enterprise XML made the tech seem outdated and drove everyone to 'cleaner' JSON, because things like XSLT and XPath were very mature and solved a lot of the problems we still struggle with in other formats.

I'm probably guilty of some of the bad practice: I have fond memories of (ab)using XSLT includes back in the day with PHP stream wrappers to have stuff like `<xsl:include href="mycorp://invoice/1234">`

This may be out-of-date bias but I'm still a little uneasy letting the browser do the locally, just because it used to be a minefield of incompatibility

replies(8): >>44394503 #>>44394794 #>>44395004 #>>44395249 #>>44395303 #>>44396380 #>>44398418 #>>44399777 #
codeulike ◴[] No.44394503[source]
Xpath would have been nice if you didnt have to pedantically namespace every bit of every query
replies(2): >>44394910 #>>44402159 #
1. somat ◴[] No.44402159[source]
Can confirm, Working programaticly with XML is not really that bad, there is a well formed query syntax(xpath), the dom api just works.

Until some joker decided to employ xml namespaces, then everything turns ugly real fast. I am not sure I can articulate why it is so unpleasant, something about how everything gets super verbose and api now needs all sorts of extra state.