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.
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
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 🚨
LOL. Speak of the devil, some slop coder just opened a massive PR on our codebase with gems like:
funcrunHandler(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…
Honestly I would expect short term instability and much better stability medium-to-long term. Those zillion little fixes are one reason why Apple stuff “just works” more often than Linux stuff
I am not sure anything about that is good.
how about checking it and working it out for yourself?
or maybe even reading the article
jesus
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.
According to Torvals/TFA:
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 🚨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.
Run… No! Wait.
deleted by creator
Just when Linux started getting really good too with game support.
While I love BSD, three just not enough support for running it on desktop. Lack of drivers and good luck playing modern games.
Honestly I would expect short term instability and much better stability medium-to-long term. Those zillion little fixes are one reason why Apple stuff “just works” more often than Linux stuff