Realistically, approximately none of the 486 code has had more than some automated testing in a virtual environment in a long time. We should assume it is bitrotted and only suitable for use on toys where subtle bugs in cache or memory management that leaked in from newer generations won't kill anyone. The time to fork the entire 486 arch and have a trustworthy result passed long ago.

It's the same situation as when Reiser3 was removed. Anyone who was using it in a new kernel could tell that performance was broken and should have been scared about the actual correctness and data integrity.

It's vaguely worded without definitions because the framers could not agree on actual definitions and each counted on their faction being in power and able to enforce things the way they envisioned. They gave up on trying to find a compromise then and we are still arguing now.

Were there other computer ads during that super bowl? Every company in an industry simultaneously choosing to spend on super bowl ads for the first time is a different signal than one company doing so.

There is 0% chance that an AI auditor will blow the whistle on their user misrepresenting reality. For a human auditor uncomfortable with their superior's report, the probability is non-zero, especially if they think someone up the chain will agree with them. It might still be a very low probability, but there exist humans who will complain in some circumstance.

The Dell trackpoints were horrible under Linux when I last used them a decade ago. Fixes were perpetually coming soon for the new hardware's handshake to be added to the kernel so they would show up as a trackpoint plus touchpad, with working independent controls. The worst case was the middle ground where the user control panels in KDE etc could see them but disabling the touchpad did nothing because actual events were routed through a common pipe with the trackpoint.

We are long past the point where software with a specific name and even user-visible version had fixed behavior. A/B tests on users, "minor updates" that change functionality that isn't exposed by the top UI, context-dependent behavior from your OS version or release or user account type, and even different software packages with the same name are all standard.

Microsoft have caused this reputation problem for themselves by embracing complexity and trying to hide it all from the customers. Figuring out how to change a behavior on my computer no longer even likely applies to other computers, and frequently the behavior is reset by an automatic update anyway.

The SEO experts claimed view duration was critical to SEO. Doing something "for SEO" doesn't require it to be an effective or even logical connection.

The protests are against basically everyone in parliament. There is no successor in office that they would accept as legitimate

And the Continental Congress thought they had a shot at peaceful revolution by offering the king power back, by having him side with them as the legislature for America and cutting Parliament out. He was smart enough not to humor them.

There are also plenty of employers who will openly say they require all employees to have clearances. There's no way around it without just leaving a gap or making something up.

After Gen Z comes Gen Alpha, apparently.

History of the World Part 2 is a show on Hulu with some peripheral involvement by Brooks. It's very uneven, like the apparently forgotten Spaceballs cartoon series.

The article says they only started disappearing in Japan over the last decade, but didn't really explain why. And since the reporting depends on machine translated press releases, they probably don't know either.

No. Crowdstrike took down all Windows machines. It took hours to a day to get most of them back up for everyone.

Southwest's application stack was most resilient and they had booking systems up and running within the day. Other airlines had their application layer synced overnight.

Delta's application layer could not recover. If all their computers had rebooted at nearly the same time, they'd have the same situation where they were offline for days. Those cascading failures had nothing to do with the initial Windows crash and lockup. Then Delta tried to cover themselves by claiming they were still dealing with the initial Crowdstrike problems for days but Microsoft refuted that and eventually Delta had to disclose the real problem to regulators and investors.

The BSODs happened to everyone globally. It was only Delta who had their application layer, including the terminal emulators talking to the non Windows databases, suffer cascading failures after they'd restored Windows.

Delta had a completely unrelated latent system design problem that meant they could not recover from the systems all going down at once.