The Enclosure feedback loop, or how LLMs sabotage existing programming practices by privatizing a public good

65 points by michiel


hongminhee

You've articulated the dilemma clearly. The feedback loop means big players already have what they need, and as you note, withdrawal would only handicap open source LLMs while increasing corporate advantage.

I think there might be a third path between these two bad options. In a recent post, I argue for what I call “training copyleft”—allowing LLM training on our code, but requiring the resulting models to be released as free software.

F/OSS has faced enclosure before: binary distribution, Tivoization, the SaaS loophole. Each time, the solution wasn't access denial but evolved licensing that demanded reciprocity. The same principle could apply here.

It's admittedly uncertain whether this can work, and enforcement would be challenging. But I think it's worth pursuing, because the alternative—watching this play out as you describe, with no meaningful resistance—seems worse.

The rent-seeking dynamic you identify is real. The question is whether we can establish norms and legal frameworks now, while the conversation is still open, or whether we wait until those norms are set entirely by corporate interests.