Forgot your password?
typodupeerror

Comment sarcasm aside (Score 1) 43

There IS a place for AI as a coding assistant. If used right by someone who COULD write good code from scratch AND who is well-versed in using his AI tools, it could actually save time.

In very limited problem domains, non-AI program-generators and LLM-"AI" program-generators can actually produce usable, correct, reasonably efficient code almost all of the time. But so could a reasonably competent programmer who was an expert in the problem domain.

In any case, using AI is likely to use a lot of electricity.

Comment Re:Not a vibe-coding problem (Score 2) 43

Old way for a small task an entry-level person could do in 2 weeks solo: a week to design, a few days to code, a few days to unit test

New way - "official/what you tell your boss": a few hours to design/decide what you want the output to look like and rough-draft your prompts a hours to "code"/prompt the AI, including iterations, and a few hours to test the results.

New way - "reality/what you actually do": design? what's that? a few hours to iteratively create prompts until you get output that "feels good," and testing the results - yeah, right, who has time for that?

Sigh.

Submission + - AI finds signs of pancreatic cancer before tumors develop (nbcnews.com)

fjo3 writes: An AI model developed at the Mayo Clinic in Rochester, Minnesota, detected abnormalities on patients’ CT scans up to three years before they were diagnosed with pancreatic cancer, according to research published this week in the journal Gut.

The scientists behind the model, which is now being evaluated in a clinical trial, trained it by feeding it CT scans from patients who had been screened for other medical conditions then were later diagnosed with pancreatic cancer. The team then had radiologists review the scans and compared their ability to find early signs of cancer to that of the AI model. The model was found to be three times better at identifying the early signs.

Submission + - Copy Fail exploit lets 732 bytes hijack Linux systems and quietly grab root (nerds.xyz)

BrianFagioli writes: A newly disclosed Linux kernel vulnerability called Copy Fail (CVE-2026-31431) allows an unprivileged user to gain root access using a tiny 732-byte script, and it works with unsettling consistency across major distributions. Unlike older exploits that relied on race conditions or fragile timing, this one is a straight-line logic flaw in the kernelâ(TM)s crypto subsystem. It abuses AF_ALG sockets and splice to overwrite a few bytes in the page cache of a target file, such as /usr/bin/su. Because the kernel executes from the page cache, not directly from disk, the attacker can inject code into a setuid binary in memory and immediately escalate privileges.

What makes this especially concerning is how quiet it is. The file on disk remains unchanged, so standard integrity checks see nothing wrong, while the in-memory version has already been tampered with. The same primitive can also cross container boundaries since the page cache is shared, raising the stakes for multi-tenant environments and Kubernetes nodes. The underlying issue traces back to an in-place optimization added years ago, now being rolled back as part of the fix. Until patched kernels are widely deployed, this is one of those bugs that feels less like a theoretical risk and more like a practical, reliable path to full system compromise.

Slashdot Top Deals

Human beings were created by water to transport it uphill.

Working...