A lot of critiques of capitalism (not to discount them entirely) ignore factors like consumer and inter-agency choice. And ironically, "free market"eers ignore the importance/power of unions as a market mechanism. We collectively have the ability to stop using companies that abuse consumers, the environment, etc., but largely fail to use it and have developed a culture of ridicule against people who do. Unions are a critical factor in suppressing corporate abuse of workers and consumers.

You use it for pointers and double check the results. I’ve had a lot of luck using it to explain terminology for complicated specialized tasks for trades work and stuff recently.

Were you doing any serious “devops” at the time? I didn’t struggle with “serverless” knowing that otherwise I had to manually provision servers, virtual or bare metal.

Ironically this conversation shows the issue with the use of the word “psychichal”.

“Function-based”, “image-based” would have been slightly more accurate terms.

Wireless devices aren’t actually “free of wires”, it’s that you don’t have to deal with wires (or significantly less, since you still have to charge them etc., save for wireless charging). So that’s not really new either.

I never would. And never have.

When you realize they actually have an adverse incentive to support indiscriminate bombardment…

https://en.wikipedia.org/wiki/Diffusion_of_responsibility

“Fanatical” would be a word to use there maybe.

Years

YYYY

±YYYYY

ISO 8601 prescribes, as a minimum, a four-digit year [YYYY] to avoid the year 2000 problem. It therefore represents years from 0000 to 9999, year 0000 being equal to 1 BC and all others AD, similar to astronomical year numbering. However, years before 1583 (the first full year following the introduction of the Gregorian calendar) are not automatically allowed by the standard. Instead, the standard states that “values in the range [0000] through [1582] shall only be used by mutual agreement of the partners in information interchange”.[20]

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[21] An expanded year representation [±YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign[22] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on.[23]

If you’re being handed a string 2022424-12-19T14:44:39Z, and told it’s ISO-8601, you should be able to figure it out. Really, a decent parser should be able to recognize that on its own (just use {4,} instead of {4} in regex). It does mean that non-hyphenated YYYYMMDD shouldn’t be used (I typically never see them encoded that way) - but even if you did, you’d just do (\d{4,})(\d{2})(\d(2}).

Planes crashing out of the sky wouldn’t have been inconceivable. Say you have two air traffic control systems that are synchronizing - one handles dates with a modulo 100 (00-99, i.e. 1900-1999), another handles them in epoch time. All of a sudden the two reported time + positions of two different planes don’t match up by a century, and collision projection software doesn’t work right. I’ve seen nastier bugs than that, in terms of conceptual failure.

At no point is that a theory about a “conspiracy” either, IDK why you’re bandying that term around.