Arguably these legal systems are the conceptual basis for our modern law system because they are used pedagogically in this way.
"New" governments had a habit of writing up founding documents that focus on the "new stuff" and waving in "all the old stuff" that doesn' conflict with the "new stuff" via a few throwaway phrasings.
I have worked as a programmer for years and at work have had absolutely zero times I have needed to know x86-64 commands like ADD, JMP, MOV etc.
Actually it is good I learned about other processors since once on a personal project, I compiled C code but it ran different on little endian and big endian chips. If I hadn't learned about other architectures I would have been more perplexed.
As someone else said, law schools teach about Roman law and other forms of law not immediately vocationally valuable. Also - I learned something about non-standard computer architecture as an undergrad, and many people go on to become programmers with a BSCS, lawyers typically go on to get a JD after doing undergrad.
I'm sorry, I thought we were talking about computer architecture?
Barring concerted effort, a U.S. law student will not leave school with detailed knowledge of any particular jurisdiction.
Then graduates take the bar, where they are more or less quizzed on 18th century English common law, because most states use a bar exam that is not specific to each state’s law.
I agree that University courses shouldn't purely be vocational training; there's value to personal growth and pure academia that doesn't have a 1-1 overlap with the corporate world.
That said I certainly appreciate that my time at University has been largely applicable at work. Doing both where possible is likely a valuable goal.