I think what you are proposing is "long term occupation", and I agree that *can* be made to work. It does, however, have significant costs, and opportunities for disaster. The US occupation of Japan, and the Allies occupation of Germany were examples of successes, but it's not clear that this either could have been done in Iraq, or that there wouldn't have been intolerable costs. And there clearly wasn't the long term political will to accomplish it.
Naive is a version of untrustworthy. Ask your Nigerian Banker.
So what you're saying is that there is old hardware that will only work if you make your system insecure. OK.
FWIW, I don't consider any system that allows remote sessions to be secure. Period. So you need to isolate such systems. (This isn't an argument that you shouldn't run such systems. Just that you should take precautions.)
As an aside, I think that allowing compressed files to be expanded with the execute bit set is also a security hazard...just one that's probably worth the cost. In most circumstances. (And hazard isn't the same as hole. Not quite.)
You are making the assumption that they didn't intend this result. Or at least that they weren't aware that this would be the result. I find that quite dubious. As you say, it was obvious by inspection
OTOH, what would have been the result of disbanding the Iraqi army? You've created a bunch of people trained in violence suddenly out of work. I'm not convinced that it would have resulted in a better situation, though clearly it would be a different situation. And long term occupation would also have tremendous probabilities for disaster.
The real mistake was deciding to invade. After that I don't think there was a decent exit strategy...not if you are counting human cost. But this *must* have been obvious ahead of time, so clearly that wasn't their consideration. Who benefited? Who expected to benefit? How? It strikes me as a clearly political decision with only political gains.
True, there also needs to be a maximum length of any given law which includes in the length all other laws cited by reference.
I also think there needs to be a reasonable test for intelligibility. It's not right that everyone should understand every law, that's an impossibily high bar, but an average high school senior should. And at minimum should be able to. I can't think of a simple way of phrasing that test though that isn't of the form "Take a bunch of average high school seniors and have them write an essay about what the law means, and what it means is the intersection of what they claim it means", and that's also a poor idea, because it would eliminate everything...but I can't think of an objective "average understanding" evaluator.
Good luck ever actually getting rid of it, considering it is what every *nix gui app runs on. Even if the switch to Wayland happens, most people will still be stuck with using XWayland constantly for a decade.
How persistent is the storage over time? I've had CDs become unreadable due to media degradation...though I don't know whether it was fading of the dyes or yellowing of the covering...or some other reason...but it wasn't scratches.
OTOH, air pressure at sea level is a variable which can change significantly in even a short period of time. Still, dramatic changes don't happen, but it's better to measure it in
Well....sort of. The CMB is modified by galaxies that are too faint to see, though I don't know by how much. It's filtered by intervening dust clouds moving WRT both us and the "origin of the signals". Etc. I normally assume that this is taken account of as best we can, but it's not unmodified signal. If you look at the raw (uncorrected) observations, I don't know how much noise is present, but clearly that are signals too weak to be recognized even though detected.
OTOH, I am not a cosmologist. But I do recognize that error bars are important, and that they tend to get left out of popular articles.
Nonsense. The cat does not hate the mouse, the cat LOVES the mouse. It's delicious.
Yes. There are numerous reasons to "not fight city hall". But that doesn't mean you can't do it for a good enough reason. E.g., I use tab spacing at the start of Python lines. This causes formatting problems if I use idle, but to me its worth the cost. And I've occasionally had reasons to use a length terminated string in C...though I usually also zero terminate it. (IIRC the reason was that I needed to include 0 valued bytes in the string.)
Similarly you can use zero delimited strings in Pascal, but you need to write the support routines that you would need, and since current Pascal has a string type that isn't limited to 255 chars it they would appear to be rarely needed.
Python is an open source project. Ruby is an open source project. Squeak is an open source project. D is an open source project. Racket (scheme) is an open source project. ALL have decent language documentation. And that was just a list off the top of my head. Being an open source project is not an excuse for lousy documentation.
Did you ever try to run C on the Apple ][? UCSD Pascal was available, and worked well. C required an add on z-80 chip, and it was still a subset implementation. (Check out "Lifeboat C", though I think that was a later, and more capable version.)
So the situation is more complicated than you are assuming. I didn't get a full C compiler until AFTER I had gotten an 8086...which means probably that the IBM PC was already around.
Sorry, but the length defined strings are optional, though common in Pascal. UCSD (and other early) Pascals usually buit that into the language, but I believe that now it's a part of a standard library, and alternates can be defined (though probably not with the same name). I'm not sure why you consider Pascal data structures more "well defined" than C structs.
P.S.: Strings in C can also be handled with a length byte. The zero terminated strings are purely a library convention, and can be overridden.
FWIW fpc Pascal has a string type in it's library that uses a length value longer than a byte.