And dont pay anywhere close to what they were making.

Any subs that follow the TrueWhatever invariably turn into shit.

Hey guys, we told the AI agents to constantly look around and find something to do and so they found something to do, it must be alive.

Buy Other Stereo Equipment

Better Off Something Else

No highs no lows it must be bose

Only one of the exploit chains requires LFI, there's other paths of triggering the exploit

Before you go public, as you control all the shares. What's SpaceX going to do? You think Elmo is going to give up the shares, or is he going to issue 73 million more and dilute the price?

Sounds like 46 more targets of investigation.

2001: Windows XP ran on as little as 64mb with 128mb being the recommended.

2021: Windows 11 minum is 4gb is listed as the minimum. I've never even touched Windows 11, so I don't know if that is realistic.

The minimum specs for each system is a 64x multiple, as you said. That's a good observation. I'm pretty sure in the late 90s I was running Windows95 with 96mb and my motherboard was capped at 128mb. Negligible ram on the graphics card. It also could have only been 64mb. I don't have a clear memory of what I was running when I first got XP.

Today my PC is a partially upgraded (old) i7-4790k with 32gb ram and 10gb of ram on the video card, so approximately 448x increase in memory in ~25 years.

My Mac is 256gb unified, so ~2,730x multiple.

Still not to the Moore's Law rate!

This is probably the best sentence (and post) that I have read on Slashdot in some time. Amen.

Unless they're secretly training on all your chats despite them saying they're not.

Another thing that I have found Claude is really good at doing is taking an error from a log and doing a deep dive analysis of what happened. I give it read-only database access, access to www logs, access to application logs, access to a checked out source tree, etc. I paste in the error message (or in some cases paste in a tech support email from a user) and have it write up an analysis, a proposed response to the customer, and any recommendations (if there is a bug or actual problem).

99.9% of that can be solved with allowing the construction of new designs of reactors instead of booting the old ones back up.

Uh, huh, sure.

I've been using Claude to both understand and assist in writing new code in DB/C, an obscure dialect of another pretty obscure language called PL/B or DATABUS -- all of which are descendants of (or highly influenced by) COBOL. It's pretty fantastic. It's a codebase that is ~50 years old, hundreds of thousands of lines, with code spread throughout modules, with jump tables and gotos everywhere. The code itself is easy to read and understand, but the flow is not!

But the forced obsolescence caused by systemd is fine.