Silicon Valley Technology Commentary & Archives · Est. 2006 3,049 Posts · 2006–2026
Showing posts with label Open Source (1 posts). Show all posts

November 15, 2026

November 15, 2026 · 3 MIN READ · BY LOUIS GRAY

Should All AI-Generated Code Be Open Source?

Should All AI-Generated Code Be Open Source?

License laundering and the origin of machine code [Graphic via AI]
License laundering and the origin of machine code [Graphic via Gemini]

Should All AI-Generated Code Be Open Source?

If AI is doing all the writing and the reading, and has made the creation of software relatively trivial, quite possibly even putting us on the path to bug free code, then that process has value. But, interestingly, Jakub Jankiewicz, Creator of jQuery Terminal, suggested that all code generated with help from AI should be Open Source or released under Creative Commons to the world. Why?  As he outlines, foundation models were trained on decades of GPL and repositories scraped from the open web. His suggestion: when you ingest millions of developer hours and spit out proprietary binaries, you are essentially turning collective public knowledge into private value.

This seems like the perfect ragebait for a back and forth discussion on Hacker News on a weekend, and that's precisely what has happened, as we've seen nearly six hundred comments debating copyrightability and the U.S. Copyright Office guidelines. Predictably, this explicit use case has already been addressed that using AI tools to assist does not impact the copyright protection for the results, and that copyright doesn't extend to purely AI material, if humans were not involved.

Try getting this group to agree. Won't happen. I remember the initial debates around open source vs closed source -- as companies felt open source alternatives would erode their profit margins or produce low quality software rife with security issues. Meanwhile, practically the entire Web has been built on the back of open source software and interoperable standards, and things haven't yet completely ground to a halt.

Depending on one's hot take on AI, the sheer mention of AI involvement can basically make you feel like taking a side. If you think AI is the best thing since the invention of CGI unicorns, you think this is no big deal. If instead you think AI is going to eradicate humanity, based on the blood, sweat and tears of creatives, you want to make sure it never sees a penny. But tying open source mandates directly to machine assistance feels like fighting the last war.

Long before automated coding, developers studied Stack Overflow snippets and public repositories to build their products. Those of us masquerading as HTML jockeys searched for code examples or hit View Source to see how sites embedded tables or built nifty JavaScript crawls. The real tension is not about whether an algorithm read your GitHub commits, but about who takes responsibility when things break in production or who cashes the checks that result from your effort. Writing code is simply no longer the bottleneck. The ability to orchestrate systems and define the actual problem matters far more than generating raw boilerplate functions -- and that's before you even get to marketing and sales.

If pure machine code spawned by agents cannot be copyrighted because those bots don't hold legal rights, companies relying entirely on unedited prompts might find themselves in an indefensible position. But yeeting ones self to the other side and treating every AI-impacted function as a public utility ignores the human architectural choices required to stitch those elements into a working application. My hot take is that AI use is going to be as commonplace as a word processor, a calculator or a spreadsheet. It's just a tool, and using the latest tools doesn't make your output less valuable or owned.

Ultimately, the open source community will adapt to this flood of machine text just as it adapted to copy-pasting from forums. The winners won't be the people guarding yesterday's tools, but those who focus on what we build next, and who adapt to a fast-changing world.

Disclosures per always:
I am not a lawyer and have never been confused for an engineer. I am also not an AI, and I barely know how to use GitHub. Wow. Glad I got that off my chest.