Post B208MoKktchVfdy7c0 by Yuki@groupe-tazor.com
(DIR) More posts by Yuki@groupe-tazor.com
(DIR) Post #B204qqsra0CYRzzXYu by Yuki@groupe-tazor.com
2026-01-06T06:51:33.289Z
0 likes, 0 repeats
@ShadowJonathan@tech.lgbt that or they gonna introduce something cursed in Ansible-compatible YAML or something
(DIR) Post #B2088bZrWkJI3NGFLU by lanodan@queer.hacktivis.me
2026-01-06T07:28:23.714184Z
0 likes, 0 repeats
@Yuki @ShadowJonathan Reminds me of how Solaris uses XML files for it's service manager, because of course Sun would have picked that…
(DIR) Post #B208MoKktchVfdy7c0 by Yuki@groupe-tazor.com
2026-01-06T07:30:54.992Z
0 likes, 0 repeats
@lanodan@queer.hacktivis.me @ShadowJonathan@tech.lgbt and they're not the only ones afaik, MacOS also uses XML pretty much everywherethat was pretty popular back then
(DIR) Post #B208niRUuLBrDZx3hI by lanodan@queer.hacktivis.me
2026-01-06T07:35:49.561082Z
1 likes, 0 repeats
@Yuki @ShadowJonathan Yeah, as is JSON / YAML currently although maybe to an even higher degree due to marketing-hype.And XML… as much as I can appreciate it sometimes, the parsers almost always seem to have been written without any security in mind.
(DIR) Post #B21NIxiSRU798OxDQO by orman@furry.engineer
2026-01-06T13:40:55Z
0 likes, 0 repeats
@lanodan @yuki @ShadowJonathan are JSON or yaml any better on average?
(DIR) Post #B21NIzEOoDG5pkuEqm by lanodan@queer.hacktivis.me
2026-01-06T21:52:58.403639Z
0 likes, 0 repeats
@orman @Yuki @ShadowJonathan I'd put it this way:JSON pretty much forces parsers to only be parsers. Sadly unrelated to that JSON also means very poor extensibility and is unfit for formats like HTML or SVG.XML (and maybe YAML a bit too) meanwhile allows the parsers to transform into engines, resolving not only local XML entities but also external entities as well as DTDs* present in the XML payload.*Thankfully XML catalog is a thingAlso meanwhile, JSON-LD forces to have an engine due to part of the needed data for namespaces being over URLs due to allowing remote aliases.