If I was running a town budget I wouldn't want to insure that shit. If any vendor offered to pay for the vandalism and eat the insurance premiums and deductibles, then that is a huge point in favor of that vendor. Disasterous for their business though.

Not even downsized, more like taking a short break from the regularly scheduled fascist dystopia. The fake concern and imagary compliance is very much temporary. Once the American people lose interest and follow a new distraction, they can install 2X more cameras and 10X more AI

LLMs have certainly made people get really into conspiracy theories. *eyeroll*

The LLMs didn't just off on their own decide to look for hypervisor bugs. Users told it to look for hypervisor bugs. The timing means that multiple users did so at roughly the same time - probably in response to some news of some sort.

Believing in one person, one vote and the concept of individual liberty is playing right into their hands.

You don't have to engage if you really don't believe it is plausible that something catastrophic could happen by hooking all of our infrastructure, law enforcement, surveillance, and military into statistically-driven software stuck in a feedback loop.

To be fair, you went to war with Iraq due to faked and purposely misinterpreted intel. Not even that well faked either: much of the rest of the world called bullshit.

You did almost nuke various countries, including your own, because Strategic Air Command couldn't tell the difference between jamming and a solar storm, a jumpy guard saw a bear climbing a fence, somebody thought swans were Soviet aircraft, Nixon was a mean drunk, the moon, bombers kept dropping nukes by accident, an AT&T switch failed in Colorado, bomb detectors couldn't tell the difference between a nuclear attack and a power outage, someone accidentally loaded a training scenario onto a NORAD computer, a couple of those NORAD computers had bad chips, etc.

Wrong again.

Moreover, many of the big complex systems I've worked on were big and complex mainly because OOP nitwits had designed them. They often didn't understand how computers actually work, lost sight of the fact that they were writing a computer program, and spewed out frameworks that filled countless gigabytes of resident memory with endlessly deep layers of nothingburger abstractions. Maybe that didn't matter so much when memory was cheap, but that's no longer the case.

If you think that there's only one way to deal with large data sets, you're a just noob that needs more experience before spouting your theories.

The best irony is unintentional self deprecating irony.

TIL.

Suicide at age 52. Shame. :(

...Modern ejector seats cause spinal injuries from which full recovery is "unusual". Smashing the spines of pilots might not be the most effective way to boost morale.

$22,000 per hour. The F35 will be nearer $42,000 per hour. These are under-estimates, as they do not include price hikes, crashes that close businesses, crashing into businesses, crashing into heavily-populated sports centres, etc.

HAL 9000 was given a starship.

AI can only start a nuclear war if someone gives it launch control over nuclear missiles. A coin flipping device could also start a nuclear war if someone gave it launch control over nuclear missiles.* If a coin flipping device can trigger the doom scenario just as well as AI is AI really the problem?

Aka you told it to drive out of control.

They told it to take a friggin' test.

If your code doesn't compile in Rust just wrap it with unsafe { }
Hacking around and doing it the wrong way is much easier than figuring out how to get a complicated data structure through the borrow checker and value** lifetimes.

** I think of Rust values as objects in the general sense.

C++ is just as much of a sieve as C, only more obtuse.

"Object models" are an anti-feature.