Comment by toast0

20 hours ago

I'm no Carmack, but everything I've released as open source is a gift with no strings (unless it was to a project with a restrictive license). A gift with strings isn't exactly a gift.

If you take my gift and profit, it doesn't hurt me, there were no strings. Your users presumably benefit from the software I wrote, unless you're using it for evil, but I don't have enough clout to use an only IBM may use it for evil license. You benefit from the software I wrote. I've made the world a better place and I didn't have to market or support my software; win-win.

I've done plenty of software for hire too. I've used plenty of open source software for work. Ocassionally, I've been able to contribute to open source while working for hire, which is always awesome. It's great to be paid to find and fix problems my employer is having and be able to contribute upstream to fix them for lots more people.

I'm the same, I've seen some of my stuff pop up in the weirdest places and I was ok with it. But I understand and respect that people who published code under restrictive licenses may have a problem. The GPL is absolutely "NOT-a-free-gift" license, in both wording and spirit.

If someone published something as MIT and doesn't like it being used for LLM training, yeah that person can only blame themselves.

For GPL, it all depends if you consider a LLM "derivative software" of the GPL code it was trained on. It's fair to have an opinion on that either way, but I don't think it's fair to treat that opinion as the obvious truth. The same applies to art, a lot of it is visible on the Internet but that doesn't make it "a gift".

  • To clarify, GPL is not a free as in "free gift", but it is free as in "freedom".

    The giving back part is strongly related to the "freedom", not related to whether you profit from it or not.

    • > To clarify, GPL is not a free as in "free gift", but it is free as in "freedom

      To clarify further: "freedom" for the end user, and not the developer leveraging GPL code in their software product.

      1 reply →

  • MIT license requires credit.

    • Ahhhh yes that's one that lawyers might have fun with. MIT says:

      > The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

      My personal thought on that: it's going to be almost guaranteed that, if an LLM is producing stuff it clearly derived from a certain piece of code XYZ, it will also be capable of producing the correct answer to the question "what's the license for XYZ?" And lawyers will successfully argue that this counts as "included".

      1 reply →

Presumably you are licensing your code as MIT or a similar license.

Not all code is licensed that way. Some open-source code had strings attached, but AI launders the code and makes them moot.

  • If you want to attach strings which involve restricting access, open source is not the way to go.

    • You're right - the reality of the world today is that open-sourced code is slurped up by AI companies, all questions of legality/ethics aside. But this was not the reality of the world that existed when the code was licensed and released. That is why it is easy to empathize with code authors who did not expect their code to be used in this manner.

      1 reply →

    • By far the most popular strings involve restricting restricting access. That is, viral licenses which require derived works to also be open source.

  • No one cares. Copyright in general is done, and we are all stronger now. Don't fight AI, fight for open models.

    • Great! So I assume it is now Completely Fine to rip Netflix / Hulu / Disney+ / whatever and share it with everyone I know?

      Copyright isn't "done", copyright has just been restricted to the rich and powerful. AI has essentially made it legal to steal from anyone who isn't rich enough to sue you - which in the case of the main AI companies means everyone except a handful of giants.

      1 reply →

    • The thing is, copyright is not done. The legal framework still exists and is enforced so I am not sure how to read your reply as anything other than a strongly worded opinion. Just ask Disney.

      I use AI every day in my dev workflows, yet I am still easily able to empathize with those who did not intend for their code to be laundered through AI to remove their attribution (or whatever other caveats applied in their licensing.)

      3 replies →

    • I know tech normally breaks the rules/laws and have been able to just force through their desired outcome (to the detriment of society), but I don't think they are going to be able just ignore copyright. If anything those who depend on copyright see how ruthlessly/poor faith tech has treated previous industries and/or basically anyone once they have the leverage.

      Tech is becoming universally hated whereas before it was adored and treated optimistically/preferably.

      1 reply →

    • there are no open models. none. zero.

      there are binary files that some companies are allowing you to download, for now. it was called shareware in the old days.

      one day the tap will close and we'll see then what open models really means

      4 replies →

I'm not sure that's true. You may not see it that way, but you're still participating in a capitalist society. Not that there's necessarily something wrong with that, but you have to acknowledge that and act accordingly.

Most people wouldn't work for free. Yet companies like OpenAI, Anthropic and Google exploit OSS maintainers like that. They're winning and we're losing. And if they have their way, millions of programmers will lose their livelihood.

One of the changes I have made in recent years is to move to the unlicence. I am ok with people using my code. I'm not ok with people saying that other people shouldn't be allowed to use my code.

Most open source licenses have strings attached, the terms of the licence say what those “strings” are. Like requiring attribution.

That sounds fun. I am trying to find potential employers who need me to write or fix code, and ideally contribute upstream along with it. Any ideas where to start? I am thinking something "chill". I am trying to avoid large corporations.

> If you take my gift and profit, it doesn't hurt me

My opinion is that it actually hurts everyone when the open source commons are looted for private profits

  • Carmack is wealthy, and will do OK even if every single software-related job is terminated and human-mediated code-generation is relegated to hobby-status. Other people's milages vary.

    My motivations are very different: the projects I authored and maintained were deliberately all GPL-licensed, my contributions to other OSS are motivated by the desire to help other people - not to an amorphous "world."

    • Correct. And certainly not to people and companies who'd like to use my work to deny end users the rights to control their computing.

      That's the whole point of the GPL to me. The code I release is not an unconditional gift. It definitely has strings attached on purpose.

      LLMs completely break this. I'm helping very rich people build the systems they impose to the world and that have awful externalities, and these systems help others build proprietary software. I can't say I'm too happy about this.

  • How much do you think people would pay for this patch?

    https://github.com/openssl/openssl/pull/1320

    If you had to pay for it seperately, would you include it in anything?

    And yet, including it everywhere helps people with clients that can't be upgraded. Maybe less now, rsa_dhe is not deployed so much and hopefully windows 8 is also not deployed so much.

It's interesting that the "natural reaction" to releasing an open source project, have it be successful, and have some Amazon "steal" it (leave the argument aside, that's how people will feel, big company makes money using the gift) is somehow worse than if you work for Big Company, they pay you, and then later use your code to make billions.

  • Yeah, it's rhymes with people getting mad about pharmacos charging outrageous prices for life saving drugs they developed in order to charge outrageous prices. In both cases (drugs and OSS) it's an ugly process that produces great and greatly uneven value to humanity, but the alternatives are less value overall, even to those on the losing side of the uneven value.

    • >it's an ugly process that produces great and greatly uneven value to humanity

      That'd be far more believable if it weren't for the fact a vast majority of the research is publicly funded for those drug companies. They have no issues selling their drugs for less money in other markets while still turning a profit. And there's absolutely no indication they'd cease to exist with just outrageous profits, not "crippling entire economies" level profits.

      3 replies →

  • Seems pretty understandable to me. In the former, you work on something hoping that real people will find it useful. In the latter, you're explicitly doing work for a paycheck.