this post was submitted on 11 Aug 2026
282 points (96.4% liked)

Technology

87162 readers
4400 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
282
Linus Torvalds says AI has made 'huge' Linux kernel updates the new normal (www.theregister.com)
submitted 3 days ago by General_Effort@lemmy.world to c/technology@lemmy.world
136 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] TheFogan@programming.dev 50 points 3 days ago (1 children)

I am not sure anything about that is good.

I mean it's good and bad, basically AI is finding a bunch of serious zero days... which is causing a lot of updates to need to be happening now, and that is kind of open source philosophy of security by obscurity isn't the goal.

[–] nymnympseudonym@piefed.social 23 points 3 days ago (1 children)

AI is finding a bunch of serious zero days

According to Torvals/TFA:

most of this is just lots of tiny fixes. It's pretty much spread all over - drivers (gpu, sound, networking, you name it), filesystems, core networking, arch code

[–] uuj8za@piefed.social 15 points 3 days ago (2 children)

most of this is just lots of tiny fixes.

If it's anything like Claude on our codebase then:

const id = "foo"
// ^^^^^ WARNING!!!! GO MIGHT NOT BE ABLE TO ALLOCATE THE MEMORY FOR THIS STRING!
// Here's an Enterprise String Implementation to guarantee this assignment works.
// Severity: High 🚨
[–] uuj8za@piefed.social 13 points 3 days ago* (last edited 3 days ago) (1 children)

LOL. Speak of the devil, some slop coder just opened a massive PR on our codebase with gems like:

func runHandler(h: Handler)  
// ^^^^^^ ERROR: runHandler will panic if h is nil  
// Severity: High 🚨

Uh... yes? Do you not know how pointers work? That's the point? You want to be able to run runHandler(nil)? That doesn't make any sense. That's clearly a mistake and we should loudly fail.

type OptionsWrapper struct {  
  Foo bool  

  otherOpts other.Opts  
}  
// ^^^^^^ ERROR: OptionsWrapper hides options only available in other.Opts.  
// Severity: High 🚨

Uhh... yes? That's the whole point of OptionsWrapper. To hide stuff otherOpts. It's a wrapper.

This type of clanker output is why another slop coder opened a PR on one of our repos, angry because he said Claude said that one of our functions was deceptive. Claude said the description and docstring was misleading and we should change it.

Our function was called RunNoWait() and, hold on, you may be surprised by this, Claude was, what this function does is run something... and then it.... does... NOT wait. wtf. I know. Shocking. Misleading, deceptive name. Claude wrote some big manifesto about why the docs were misleading and rewrote the function to add a wait. 🤣

The dude backed down eventually, but he insisted we add more paragraphs of clarification to the function docs...

Whatever. Let the slop flow..... I give up.

[–] john_lemmy@slrpnk.net 4 points 2 days ago (1 children)

Run... No! Wait.

[–] Valmond@lemmy.dbzer0.com 1 points 2 days ago

Yeah runAsync is what I'd call it, runnowait is kind of ambiguous IMO. Or just make a comment...