undefined

points

[-]

Thanks for the comment! You guessed it, I did use LLMs during development. While the strict definition of a "clean room" design can be debatable when AI is involved, I'd consider this a "light-gray room" approach. There is no direct code plagiarism here: Kakehashi is written from scratch in Rust, whereas Darling is built on C/objc. Furthermore, the architecture is fundamentally different—Darling relies on kernel-level emulation, while Kakehashi is purely focused on a lightweight userspace approach for Linux ARM. In my prompts, I explicitly restricted the use of proprietary components. Ultimately, the codebase speaks for itself, and I welcome everyone to audit the repository! Thanks again!

by 13rac13 hours ago|

parent|

[-]

FWIW Darling runs in userspace too.

What do you mean by "proprietary components"?

by vlad_kalinkin3 hours ago|

parent|

[-]

Thanks! What I meant is that Kakehashi doesn't require a custom Linux kernel module (LKM). Kakehashi operates completely without root privileges or kernel-level modifications.

By "proprietary components," I meant that in my prompts, I explicitly forbade the copying or direct implementation of private Apple code. Of course, since LLMs are a bit of a black box, it's hard to be 100% certain about everything it synthesized under the hood, but the clear intent was to stick to public ABI definitions and standard open specs.

by billyjobob4 hours ago|

prev|

[-]

Darling is written in a different language so I don't think the LLM would copy paste code from it directly. But it is the main (only?) prior art, so it could be argued that everything the LLM knows about how to do this came because it read and understood Darling, i.e. if Darling didn't exist it may still be able to do this but it would have to figure it out from first principles.

Not saying it happened here, but it's an interesting thought experiment: what if you order an LLm to achieve the same goal as a popular open source project, using all the lessons learned and pitfalls faced by that project, but not to copy the code. Indeed, LLM code is now often better than human code, so direct code copying would be a disadvantage. Humans are certainly inspired by other projects like this all the time and it isn't considered plagiarism.

by rvz4 hours ago|

parent|

[-]

> Darling is written in a different language so I don't think the LLM would copy paste code from it directly.

Just because it is written in a different language does not mean that it is a clean room implementation. The logic from Darling might as well have been lifted and then rewritten by a human or an LLM agent.

> Indeed, LLM code is now often better than human code, so direct code copying would be a disadvantage.

Is that why coding agents such as Claude Code and Codex have so many bugs in them? This is entirely dependent on the language chosen with the humans behind the decision to review and accept some of the changes.

> Humans are certainly inspired by other projects like this all the time and it isn't considered plagiarism.

Humans (researchers) also appropriately credit the work that inspires them, especially in experiments and research.

by nxc183 hours ago|

parent|

prev|

[-]

> Indeed, LLM code is now often better than human code

lol. Find better humans.

by sterlind3 hours ago|

parent|

[-]

it depends on your prompting. LLMs can generate beautiful code, or absolute slop.