That ain't the same thing.

This thing is doing things you didn't tell it to. It might even do things you explicitly told it to not do. It is not a case of "well, you could've forseen this as a consequence if you had been careful" like your campfire. My example is only a bit silly, it is absolutely possible that an AI agent will decide to hack NASA because you asked it for some data for a school project. Even in the broadest possible sense, that does not fall into stuff that the law so far has considered to be in the domain of negliegence.

AI agents do stuff you could not possibly have expected. Heck, I asked Claude a fairly simple knowledge question yesterday and it wanted to read from /dev/null. There is no argument you can make that would convince a jury that I should in any way have expected that and taken precautions. In a hypothetical world where a read from /dev/null randomly kills a puppy somewhere on the planet, I don't think I would've been convicted.

That statement is only true if the total economic outcome is exactly the same for the taxpayers, something that is rarely true.

Not surprising to find someone 'brave' enough to downvote that. What a hero for the white power cause!

And what a horrible piece of Lost Cause propaganda that movie is. It doesn't say much that's good about the people who made it, who bought tickets, or who continue to hold it up as an example of a 'great classic' even today.

I looked up the press releases Siemens put out when they bought Altair for $10 billion, and who would have guessed, it's part of their AI-push:

Translation: We are looking at our options on how to extract as much money as possible from the users of this software.

I was not disappointed, but neither was I impressed.

They did a competent job of trotting out the nostalgia bits. I would even go so far as to say they did a better job of mixing cartoon physics with the real world than Who Framed Roger Rabbit or Space Jam. It felt like a real world movie with toons in it rather than a cartoon with real people in it.

Having said that, I had nobody to root for so it didn't engage me. The story did a poor job of making me care.

The big problem Coreboot faces is the initialization of the chipset and configuring memory timings, which sometimes requires documents under NDA or time consuming reverse engineering.

It's also supported on some newer hardware like Framework and System 76 systems.

It happened when you got old and apparently didn't notice.

BTDT.

I guess it's time to RTFA, because I have only the vaguest notion of how you might do that, and zero idea how you could get anything like a tolerable framerate.

Maybe I'm missing something, but I don't believe SQL includes client data rendering. At least not any SQL implementation I've ever worked with. There's always a client that has to interpret SQL data and convert it into a rendered frame as well as send user input back to SQL as a query.

That would seem to be enough of a limitation to 'Doom on SQL' to make the total project... doomed from the start. It remains an interesting exercise in getting SQL to do the rest of it. As long as the code to do so is elegant, it doesn't really matter how Rube Goldberg it gets.

In fact, I might even be more impressed as the SQL gets more convoluted.

Back in my day, it was popular with boys about 9 and up. But it was a bit of a niche game - it had its die-hard fans, and a whole lot of people who never played it.

Isn't "Mexico" from a native Mesoamerican word, and not from a Hispanic language at all?

Pretty much this. Element has it issues, but the major problem is that users expect it to work like Teams or whatever they were using before the switch so they complain. When our company switched to Elements a year ago the major complaint from users was that it didn't work like the previous application.

Personally I think Teams is absolute shit and I prefer Elements, but that's just my opinion