https://www.huygens-fokker.org/scala/

Note also that certain musical traditions were suppressed or eradicated due to their unfortunate habit of using dissonant notes such as minor seconds, as opposed to the consonant traids favored by a particular group recently in power around the world. Happy Easter!

  Ordinarily M. de Villefort made and returned very few visits. His wife
  visited for him, and this was the received thing in the world, where
  the weighty and multifarious occupations of the magistrate were
  accepted as an excuse for what was really only calculated pride, a
  manifestation of professed superiority—in fact, the application of the
  axiom, _Pretend to think well of yourself, and the world will think
  well of you_, an axiom a hundred times more useful in society nowadays
  than that of the Greeks, “Know thyself,” a knowledge for which, in our
  days, we have substituted the less difficult and more advantageous
  science of _knowing others_.

  I didn't look closely at most of the code but one thing that caught my eye, pid is not safe for tempfile name generation, another user of the system can easily generate files that conflict with this. Functions like mktemp and mkstemp are there for a reason. Some of the other "safety" checks make no sense. If the LLM code generator is coming up with things which any competent unix sysadmin (let alone programmer) can tell are obviously wrong, it doesn't bode well for the rest.

The next AI winter can't come soon enough…

When was that? My introduction to Excel was in the 1990s when a scientist asked about data corruption, and my response was "oh, yeah, Excel does that, you need to fiddle with these options and hope the options do not get turned off, seeing as companies may randomly screw over user preferences". The look in their eyes...they probably had done a whole bunch of data entry before they even noticed the corruption. Anyways, a few decades later those genomes got renamed, for some reason or another. Other customers came to me and pleaded, please do not install Word 6, it's bad, and I was like, well, be that as it may, but Microsoft has broken the file format, again, so if someone sends you a Word 6 document you will not be able to read it. They've got you over the barrel, perhaps consider not using their software? Unless you like being chained to that main-mast, of course, don't shame the kink! Later on a coworker said, try Visio, and I was like, this is sort of bad, and they were like, yeah, it was better before Microsoft bought it. So, when was Microsoft not producing kusogeware? Sometime during the semi-mythical 80s, perhaps?

For data or code hiding the Acme::Bleach Perl module is an old example though by no means the oldest example of such. This is largely irrelevant given how relevant not learning from history is for most.

Invisible characters may also cause hard to debug issues, such as lpr(1) not working for a user, who turned out to have a control character hiding in their .cshrc. Such things as hex viewers and OCD levels of attention to detail are suggested.

  man -O tag=L ls

  man -akO tag Ic=ulimit

  #!/bin/sh
  man -akO tag="$1" any="$1"

  function info { /usr/bin/info "$@" 2>/dev/null | $PAGER; }

The contrast with only JSON is far too simplistic; XML got dropped from places where JSON is uninvolved, like why use a relational database when you can have an XML database??? Or those config files on unix are for the most part still not-XML and not-JSON. Or there's various flavors of markdown which do not give you the semi-mythical semantic web but can be banged out easily enough in vi or whatever and don't require schemas and validation or libraries with far too many security problems and I wouldn't write my documentation (these days) using S-expressions anyhow.

This being said there probably are places where something that validates strictly is optimal, maybe financial transactions (EDIFACT and XML are different hells, I guess), at least until some cheeky git points out that data can be leaked by encoding with tabs and spaces between the elements. Hopefully your fancy and expensive XML security layer normalizes or removes that whitespace?