News for hackers. Stuff that matters.
Re:XML is almost always misused by altmind on Tuesday October 29, 2019 @04:30PM (#21391630)
Can I have my gripe with apple plists?

<key>CFBundleDisplayName</key>

<string>TextEdit</string>

<key>NSHumanReadableCopyright</key>

<string>Copyright 2019</string>

This may be perfectly parsable by a SAX parser storing some state, but its totally not processable by xslt.

Re:XML is almost always misused by mikl on Tuesday October 29, 2019 @04:56PM (#21391924)
Yeah, that's awful XML. Ironically, they used to have a decent readable format in NeXTStep, it was only later it was XML-ified.
Re:XML is almost always misused by k__ on Tuesday October 29, 2019 @04:40PM (#21391751)
How old is this format?

I had the impression mobile was some new try at frontend tech, but somehow iOS and Android threw a whole bunch of outdated stuff at me.

I mean, before the iPhone I designed a XML based ETL config system and tried to avoid all the common XML errors, then I start doing a mobile app 10 years later and it's like all that knowledge was forgotten...

Re:XML is almost always misused by spiralx on Friday November 01, 2019 @11:54AM (#21420135)
I remember when Neverwinter Nights 2 came out touting that all of its data files were in XML for ease of modifying in user extensions. So I had a look and was it XML? Was it fuck, it was like a GeoCities novice's idea of how to code HTML - absolutely unparseable in any way unless you're the idiot who decided what the codebase needed was another shitty homegrown parser.

And yes, plists suck and make your XPath selectors ugly, although you could write a function to abstract them out.

Re:XML is almost always misused by nwellnhof on Tuesday October 29, 2019 @10:33PM (#21394164)
> but its totally not processable by xslt.

It's a bit inconvenient but perfectly processable with XPath:

    /dict/key[.='CFBundleDisplayName']/following-sibling::string[1]