Earlier quoted context omitted.
Because PRs with AI need to be reviewed with a lot more scrutiny, simply because AI is good at generating code that looks good, but isn't necessarily correct. So now you're looking at a PR that at face value looks good, but doesn't reflect the author's skill and understanding of the subject. Meaning now you shift more work to the owners of the codebase, as they have to go through those verifications steps.
This makes 0 sense. It shouldn't matter if AI wrote the PR or a human.
No AI in Node.js Core
41–43 of 43 posts
It makes sense, because humans and AI write code different. Because humans aren't AI. The types of mistakes AI writes into code would never be done by a human.
Re: No AI in Node.js Core
#42Earlier quoted context omitted.
Bun has claude code generated commits as we speak (as robobun).
Which does pull into question the future stability or quality of bun. As much as I don’t think nodejs should ban AI, the quality of some recent robobun AI commit message and code quality looked like hallucinated slop to me.
Maybe? I've seen human code that looks like hallucinated slop, doesn't mean it should be accepted.
Re: No AI in Node.js Core
#43Earlier quoted context omitted.
How would you go about breaking up this particular set of functionality into smaller PRs, exactly? It's meant to introduce a virtualized file system... the size is dictated by the feature itself. Also, no mention at all regarding the test coverage, or impact if any on existing code paths specifically.
There's multiple features, not just VFS.
So, like a 17.5k line change just for VFS? That'd be so much smaller and easier to reason with.