News for hackers. Stuff that matters.
Re:Why Node.js needs a virtual file system by Dylan16807 on Tuesday March 17, 2026 @03:30PM (#47417118)
If there's a "the original" the LLM is copying then there's a problem.

If there isn't, then (b) works fine, the code is taken from the LLM with no preexisting license. And it would be very strange if a mix of (a) and (b) is a problem; almost any (b) code will need some (a) code to adapt it.

Re:Why Node.js needs a virtual file system by lmm on Wednesday March 18, 2026 @01:19AM (#47421834)
> the code is taken from the LLM with no preexisting license

That's not good enough to comply with (b). The code must be specifically covered by an open-source license, it's not enough for it to just not have a license.

Re:Why Node.js needs a virtual file system by Dylan16807 on Wednesday March 18, 2026 @01:48AM (#47421962)
There's a difference between "no license, all rights reserved" and "no license, public domain". Up until recently, you could assume that not having a license meant the former. But treating the latter as the same would just be silly.

As far as I'm concerned, public domain counts as "an appropriate open source license".

Re:Why Node.js needs a virtual file system by lmm on Wednesday March 18, 2026 @02:13AM (#47422105)
> As far as I'm concerned, public domain counts as "an appropriate open source license".

For material whose author is known and has explicitly placed it in the public domain, sure. For code that fell off the back of a truck, not so much.

Re:Why Node.js needs a virtual file system by Dylan16807 on Wednesday March 18, 2026 @04:13PM (#47430836)
I'm of course assuming the legal status quo holds, where code properly generated by LLM is also explicitly public domain. No shadiness involved.

(There's always a risk of an LLM copying something verbatim by accident, but if the designers are doing their job that chance gets low enough to be acceptable. Human code has that risk too after all. (And for situations that aren't an accident, with the human intentionally using snippets to draw out training text, then if they submit that code in a patch it's just a human violating copyright with extra steps.))

Re:Why Node.js needs a virtual file system by lmm on Wednesday March 18, 2026 @08:32PM (#47433190)
> code properly generated by LLM is also explicitly public domain

Where? I hadn't heard of any such ruling.

Re:Why Node.js needs a virtual file system by Dylan16807 on Wednesday March 18, 2026 @11:28PM (#47434549)
https://en.wikipedia.org/wiki/Artificial_intelligence_and_co...

This page has a pretty good overview.

> Both the federal and circuit courts in the District of Columbia have upheld the Copyright Office's refusal to register copyrights for works generated solely by machines, establishing that machine ownership would conflict with heritable property rights as establish by the Copyright Act of 1975.[16] As of March 2026, the Supreme Court of the United States has denied hearing challenges to the Copyright Office's decision.[17]