
We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help…
We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center.
This is because Carmack doesn't really do OSS, he just does code dumps and tacks on a license ("a gift"). That's of course great and awesome and super nice, but he's not been painstakingly and thanklessly maintaining some key linux component for the last 20 years or something like that. It's an entirely different thing; he made a thing, sold it, and then when he couldn't sell more of it, gave it away. That's nice! But it's not what most people who are deep into open source mean by the term.
> This is because Carmack doesn't really do OSS, he just does code dumps and tacks on a license ("a gift").
That is, in fact, OSS. Open source does not mean, and has never meant, ongoing development nor development with the community.
That’s just incorrect. “Open source” can mean the licensing as well as the development model [0]. It certainly has been associated with the development model since The Cathedral and the Bazaar [1].
[0] https://en.wikipedia.org/wiki/Open-source_software_developme...
[1] https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar
> “Open source” can mean
Keyword being "can"
The Wikipedia page you linked to refers to "Open-source software development (OSSD)" which implies that it's a different concept than "open source" by itself
You and Bigstrat2003 are arguing a technicality, and you're technically correct, but in context I think that's somewhat beside the point. Skrebbel and Layer8 are focused on the cultural associations of "open source" development, and this mismatch is causing everyone to talk past each other.
The original post in this thread was:
> This is because Carmack doesn't really do OSS, he just does code dumps and tacks on a license ("a gift"). That's of course great and awesome and super nice, but he's not been painstakingly and thanklessly maintaining some key linux component for the last 20 years or something like that. It's an entirely different thing; he made a thing, sold it, and then when he couldn't sell more of it, gave it away. That's nice! But it's not what most people who are deep into open source mean by the term.
Skrebbel probably shouldn't have said that Carmack "doesn't really do OSS", but what they clearly meant was, Carmack doesn't participate in the sort of community development as the Linux kernel or Apache or whatever.
I’m saying that “open source” can mean both things. The parent was arguing that it only means the licensing. I’m not arguing that it always means the development model.
> The Wikipedia page you linked to refers to "Open-source software development (OSSD)" which implies that it's a different concept than "open source" by itself
By that logic, “open source licensing” would also imply a different concept than “open source” by itself.
Note that the Wikipedia page for “open-source software” [2] states: “Open-source software is a prominent example of open collaboration, meaning any capable user is able to participate online in development, making the number of possible contributors indefinite”. That would really only be the case in the context of open-source development.
The "development model" of open source is that one person code dumps, another takes, changes it then dumps it, another picks up the copy with the changes, changes it again, and so on. Sometimes it finds it's way back.
A bazaar is a chaotic market with a million vendors, not anything remotely cooperative. The Cathedral and the Bazaar is meant to convey the idea that OSS code develops without central organization, through endless forking and cloning.
The bazaar model definitely isn't the cooperation and vibes model that the HN crowd thinks it is...
Isn't Carmack just employing the 'Cathedral' type of 'Open Source'?
The “cathedral” model refers to closed-source development: https://en.wikipedia.org/wiki/Open-source_software_developme...
Appending ‘development’ seems like a significant departure from ‘vanilla’ “Open Source” to me, and wouldn’t all development be ‘closed-source’ at least between commits, if not between pull requests?
See https://opensource.org/about/history-of-the-open-source-init... under ‘Coining “Open Source”’:
The conferees believed the pragmatic, business-case grounds that had motivated Netscape to release their code illustrated a valuable way to engage with potential software users and developers, and convince them to create and improve source code by participating in an engaged community. The conferees also believed that it would be useful to have a single label that identified this approach and distinguished it from the philosophically- and politically-focused label “free software.”
From the beginning it was about promoting the model of developing software in an open community. The licensing is a means to that, but the motivating idea is to have open-source development.
And Netscape’s release of the source code, what lead to Mozilla, was prompted by the “bazaar” ideas presented by RMS.
The 'bazaar' system is a wonderful methodology, but there is a place for the 'cathedral', and it is no less open source.
> In closed-source software development, the programmers are often spending a lot of time dealing with and creating bug reports, as well as handling feature requests. This time is spent on creating and prioritizing further development plans. This leads to part of the development team spending a lot of time on these issues, and not on the actual development.
So, in closed source you work on bug reports and feature requests. In open source you work on development. But it's the closed source people working on building a cathedral.
I understand what they're driving at, but this is still the stupidest description of the analogy that I've ever seen.
"Open source" means the source code is open to the public for reading and copying. Licenses have complicated the idealistic definition to restrict copying, but that is only within the context of taking credit (ie implicit relicensure). The only winning move is not to play the game at all.
It's been a conflation issue (and major point of contention) since the 90s. "Free Software" and "Open Source Software" are two different things that have traditionally been used together to promote the rights of the user and the dissemination of knowledge in software development.
Edit, see:
I agree but he's arguing with people who's personal attachment to their OSS work goes a lot deeper than "I did a few code dumps back in the day".
It was stupid of me to say that he does "not really do OSS" because that opened the door for all kinds of definition arguments. That's a super tired discussion and it wasn't really my point. I can't edit anymore but I meant to say something like "doesn't do OSS in the same way as a large % of the OSS community".
It’s not open source in the way anyone thinks about the term. He isn’t maintaining free software in the open
I have the same attitude as Carmack. I have several libraries and sites I maintain as well as contributing to several popular open source projects. I still have his attitude about this. Both my open source and my ongoing maintenance are gifts. I'm also free to stop giving when I don't feel like it.
> It's an entirely different thing; he made a thing, sold it, and then when he couldn't sell more of it, gave it away.
You're right and it's worth pointing out that a lot of open source has the opposite lifecycle: the authors make a thing, aren't sure how to sell it, so they open source it and hope to eventually sell something peripheral, i.e. "open core" with paid plugins or enterprise support.
In these cases, open source isn't a gift so much as a marketing strategy. So it makes sense the maintainers wouldn't see LLM training on their code as a good thing; it was never a "gift", it was a loss leader.
the authors make a thing, aren't sure how to sell it, so they open source it and hope to eventually sell something peripheral
I know it sucks but we need to admit that this doesn't work and we need to beat the hope out of people. You aren't going to make money later. The very few cases where it worked were flukes or fake.
There's been something lost over time about the philosophy of open source. It appeared at a time when it was becoming apparent that computers represented a new type of technology where you couldn't just "look under the hood". An independent mechanic or machinist could repair a car to spec. A carpenter didn't need original blueprints of the house to create an addition. You could disassemble a typewriter or a sewing machine and with some ordinary skill actually manage to figure out how it worked. With compiled software the bar to understanding by the owner or operator was raised significantly. Open source was about being able to actually work on the thing you owned.
Edit: Note that the original term was Free Software, but there's a long history of politics about why the two are different.
Indeed. Maybe it's just a function of passed time, but it feels like people surrounded by hustlers - including themselves - look at this and think "what's the hustle behind this?" because they can't imagine anyone doing this for any other reason. I get it, but it's quite sad.
It's a function of the economy going in the shitter, with food and housing prices tripling or quadrupling while wages go up 5 or 10%. People want to be paid for their work because they can't afford to pay rent giving gifts away, and hustling is the way to survive because there aren't enough jobs or even if they have a job it's not enough.
Though I agree that a healthy, vibrant, open source software project requires community and merge maintainer(s), open source "code dumps" (contributions of one's work for others to share) are open source.
There's no need to shame or diminish people into a different open source contribution pattern.
We can be grateful for open source code dumps with no nxpress or implied commitment to future performance. We aren't entitled to ongoing support or ongoing development.
He also (presumably) doesn't have to worry as much about money as many OSS folks might, so dual licensing (as a means to keep working on the OSS version while also making ends meet) is likely not something he would consider.
He also started an AI company, right?
> He also started an AI company, right?
Yes, but IIRC it's different than the current "download the internet" large language model approach. More like learning to play video games or something.
Then by your definition, SQLite isn't open-source because it's a code dump with a license, but outsiders are not allowed to participate in shaping (the official copy of) the code.
The assumption here is that the people who maintain something in a painstaking manner did not intend people to take it and do whatever they want with it in accordance with its license?
"in accordance with its license" is the key part that's missing with LLMs. The licenses are completely ignored.
That's because licenses are an abstract complexity tacked on to a simple material reality in order "to promote the progress of science and the useful arts".
Just like many cultural rules, they keep growing in complexity until they reach a phase change where they become ignored because they have become too complicated.
> The licenses are completely ignored.
Where and when? In cases where LLM coding assistants reproduce copyleft code in someone's work assignment? The responsibility in those would be on the user, not on AI.
In reproducing code that requires the license be reproduced alongside it.
Are you doing a full search of every GPL licensed repository every time you use an LLM to ensure that it isn't giving you GPL licensed code? That doesn't seem reasonable
This is what GitHub promised years ago. Showing repositories where similar code is present so you can guess the license and use appropriate outputs.
I’m not sure whether this is implemented or not since I don’t use generative AI for coding.
Why not? Up until a year or two ago LLM pair programmers weren't even a thing.
The user would know how?
It seems to be a common view on HN that licenses and conditional access to websites should be ignored (i.e. WRT ad-blockers), but also that licenses on Open-Source Software repositories should be respected (i.e. WRT LLM training). I believe that holding these contradictory views is common, but the conflict would need to be resolved to come to a conclusion on how to proceed with LLM training.
There is no contradiction. Open source software licenses allow use without conditions. Ad blocker use does not distribute the modified web pages.
I have not seen any evidence that LLMs ‘distribute’ modified software, though they do seem capable of replicating it.
The view LLMs should respect open source software licenses is not for replication alone. Models and generated code are derived from training data.
Developers are permitted to learn from open source code with restrictive copyrights, and apply those lessons to developing other software which does not comply with the copyright of their 'example'.
As an aside, I do believe that LLM trainers are ignoring and violating many licenses, but open-source software is not a clear example of a violation.
I fail to see how mass scale reproduction of copyrighted code isn't a form of distribution.
Replication is not the same as reproduction; I can replicate an API without violating someone's license or copyright (which I would by reproducing their work).
Reproduce is a definition of replicate. And LLMs reproduced code.
You seem to be conflating copyright with access rights. Two very different things. Regardless of your feelings on either, there is no contradiction in holding different views on them.
Copyright is all about gating access, as media rights holders for sports well know.
Well no, it’s about legally gating the ability to copy so the original author doesn’t have to compete in the same market to sell his own book with every other bloke with a printing press and a copy of the book. Everything else is an addendum.
No, it's to promote the progress of science and the useful arts.
The current implementation has recently become obsolete.
Don’t confuse the social justification with the actual purpose of copyright law just because it’s written into the US Constitution that way. America didn’t invent copyright law.
That may be the reason copyright came to be, but it's much more expansive now.
That is still the meat and potatoes of copyright law.
That is, in fact, open source.
The community is not the license. The “open source” development community is a user of that kind of licensing.
You might better describe them as the open source maintainer community. I do see how ai impacts maintainers. But I’ve dumped hundreds of thousands of loc into the bucket with no hope that anyone would really maintain it. With AI it might become part of something useful. The license has many uses.
> It's an entirely different thing; he made a thing, sold it, and then when he couldn't sell more of it, gave it away.
He didn't have to give it away, but he did, and for that I thank him
Open source is literally just releasing the code under an OSS license.
Any additional meaning or steps isn't open source, it's something else...
OSS is a big umbrella. At the end of the day, if you are not hurting for money, you might be okay donating your work for AI training. Meanwhile if you’re working hard on projects while sacrificing a lot (including money) you are very much allowed to not want AI use it for training if it means financial gain for a select few at the top.
It has the same undertones as how rich people talk about philanthropy. “Look I donated a portion of my wealth that barely affected my life, I must be better than all those poor people who never donate to chariTy”.
This sounds to me like the "No True Scotsman" argument. https://en.wikipedia.org/wiki/No_true_Scotsman
I break down what you said as: "Sure, he's released code with an open-source license, but that's not real open source in the sense that matters."
I happen to disagree. OSS is OSS. AGPL is OSS. MIT is Open Source. Unlicense is OSS.
The point is not that it's not "real" open source, the point is that he has less interaction with the big part of the open source ecosystem which is feeling the brunt of the downsides of AI, namely, giant useless bug reports and PRs.
(I do agree that it's still OSS even if you never maintain it or anything.)
That framing makes more sense to me.
I agree there's a difference between publishing code under an OSS license and actively maintaining a project while fielding the flood of low-quality AI issues and PRs. Someone in the latter category is obviously closer to that pain.
I still wouldn't go so far as to dismiss Carmack's view on that basis alone, though. It just means his experience is less representative of maintainers dealing with that specific problem every day.
The thing is, he is not working in open source.
He only released his software as open source when there was no more money to be made with it. The idea being that even if it is of no use for him, is could be of use to someone else. In a sense, it is crazy to think of such actions as generous when it is what everyone should have done, but since being an asshole is the rule, then breaking that rule is indeed generous.
To me, working in open source means that your work goes to open source projects right now, not 10 years later when your software is obsolete and have been amortized. The difference matters because you are actually trying to make money here, and the protection offered by the licence you picked may be important to your business model.
John Carmack is making gifts, which is nice, but he wasn't paid to make gifts, he was paid to write proprietary software, so he worked in proprietary software, not open source. On one occasion, he gave away one of his Ferraris, which is, again, nice, but that doesn't make him a car dealer.
What do the people who are deep into open source mean by the term then, in your understanding?
He's downplaying the "social change" aspect. For many, open source/free software has a political element, at least implicitly. That element is strongly opposed to aggressive centralization of capital and surveillance power. You can point out how different licenses were always written in a way that permitted monetization/for-profit use, but that's beside the point -- the people who chose those licenses never imagined that their code would be used at this scale for this kind of purpose.
Has anyone else noticed a cultural shift around monetization of output? I think there wasn't as much back when I first started using open-source programs, both as a user, and a small-time contributor for decades now. And I've noticed this on other things too. A short while ago, someone on Reddit pointed out that something on Google Maps was wrong and so I went and submitted a fix and told them how to and I received a barrage of comments about working for free for a corporation that's making money off me.
I think if people want a revshare on things then perhaps they should release under a revshare license. Providing things under open licenses and then pulling a bait-and-switch saying "oh the license isn't actually that you're not supposed to be doing that" doesn't sit right with me. Just be upfront and open with things.
The point of the Free Software licenses is that you can go profit off the software, you just have certain obligations back. I think those are pretty good standards. And, in fact, given the tendency towards The Revshare License that everyone seems to learn towards, I think that coming up with the GPL or MIT must have taken some exceptional people. Good for them.
> A short while ago, someone on Reddit pointed out that something on Google Maps was wrong and so I went and submitted a fix and told them how to and I received a barrage of comments about working for free for a corporation that's making money off me.
Did you respond by asking them how Reddit makes money?
The anti-corporate mentality isn't new, but it does surface in different ways and communities over time. The Reddit hivemind leans very anti-corporate, albeit with a huge blind spot for corporations they actually like (Reddit itself, their chosen phone brand, the corporations that produce the shows they watch).
The Reddit style rebellion is largely symbolic, with a lot of shaming and snark, but it usually stops when it would require people to alter their own behavior. That's why you got dog-piled for doing something productive on a site where user-generated content is the money maker.
Hell, reddit hates on reddit all the time. Spez in particular is hated across the board.
Agree that they largely don't change behavior. Although I will say, I've not logged into my account since the API shenanigans and don't regularly visit the site anymore. I'm mostly just on here and fark.
Haha, that's funny. I didn't think of it at the time and I was more surprised than anything.
By the way, I have had your comments highlighted for a while now and I've never regretted it. Good stuff.
... There's a highlighting feature?
I've never publicly scolded someone for doing free work for tech monopolies but I do understand the impulse. The problem is that it's a completely one-sided relationship, and there are perfectly legitimate concerns about how the biggest tech companies are using their wealth and power. At this point I doubt much of anyone would expect a large tech company to go out of its way to lose money in order to support human communities. They take what they can, and ruthlessly kill products and services the minute they think it helps their bottom line.
Google and others don't need to rely on free volunteers, but it's certainly more profitable for them. Does Google making an extra $10B/year make the world a better place? Maybe, I don't know, but it's not crazy to think the answer is no.
It not a completely one sided relationship. I'm using google maps for free!!! That's HUGE benefit to me. That google makes money from it is irrelevant to me. They're paying me by providing a free service that I get tons of usage out all the time.
> Has anyone else noticed a cultural shift around monetization of output?
I think it's simply due to the economy being in the shitter for the non-"Capital Ownership Class".
1977-2007 was generally a good time in the US if you survived by trading your time/knowledge/expertise for a wage as most people do. This is also the time in which F/OSS came into existence.
If you had a decent job during that time, then the future looked bright and you didn't think twice about giving some of your leisure time away for free.
> 1977-2007 was generally a good time in the US if you survived by trading your time/knowledge/expertise for a wage as most people do. This is also the time in which F/OSS came into existence.
FOSS came into existence during this time because computers and the internet became available, not because it was a specific economic situation.
> If you had a decent job during that time, then the future looked bright and you didn't think twice about giving some of your leisure time away for free.
This seems like rewriting history. Tech salaries today are higher than they were back then. There was even a whole lawsuit against companies caught suppressing wages during that time. Tech compensation went up significantly after the period you cited.
MIT and BSD licenses are kind of obvious. They are academic licenses, named after universities.
The idea is that you have people paid to create something of potential value, but the value of the outputs has only a limited and indirect impact on their compensation. If someone finds the outputs valuable, they should mention it in public, to let the creators use it to demonstrate the value of their work to funders and other interested parties.
> someone on Reddit pointed out that something on Google Maps was wrong and so I went and submitted a fix and told them how to and I received a barrage of comments about working for free for a corporation that's making money off me
This tells you about Reddit's demographic and nothing else.
Remember Reddit has a dedicated sub for antiwork. It used to have a sub for shoplifting (I'm not kidding.)
> I received a barrage of comments about working for free for a corporation that's making money off me
The problem is that the big tech companies aren't holding up their end of the traditional social contract.
I like to think of the wider open source community as one giant group project. Everyone contributes what they can, and in turn they can benefit from the work everyone else has done. The work you do goes towards making the world a better place. I have absolutely zero problem filing pull requests for bugs I encounter or submitting issues on OpenStreetMap, because I know that in return I get the Linux DE and reliable maps in other towns. If you want to make it political, it's a "from each according to their means, to each according to their needs".
The big tech companies operate completely differently. They see open source contributors primarily as a resource to exploit. Submit a single fix on Google Maps? You'll get zero credit, they'll never stop bothering you with popups about "making improvements", design their map around what is most profitable to show, and they will of course log your location history and sell it to the highest bidder. And they are getting filthy rich off of it as well.
I couldn't care less about getting monetary compensation for some odd work I do in my spare time, but there's no way in hell I'm going to do free labor for some millionaire who's going to reward me by spitting in my face.
> The problem is that the big tech companies aren't holding up their end of the traditional social contract.
This analogy feels too strained.
Google gives away Maps, Gmail, and other products for free. A little UI widget inviting users to submit fixes is hardly an onerous demand.
> and they will of course log your location history and sell it to the highest bidder.
Google does not do this, no matter how many times this myth gets repeated online.
I think a lot of people in the Reddit and Reddit-adjacent world believe this is true because it gets repeated so much, but it's not true.
Ironically, Reddit makes money by packaging up user's content and selling it to 3rd parties.
The amount of value Google Maps has given me is far beyond what I'd be willing to pay in actual dollars.
I think we've all been burned by 20+ years of exploitation in the guise of "free product." Google more or less spearheaded that movement. I agree we should all be community-minded and have nice things, but when you look at how the rewards (social and monetary) are shared it's overwhelmingly disproportionate.
yes, and no. there is profit and there is excessive profit. if i build something to make my linux experience better and share that with the world, and a few consultancies use that to make the linux experience for their customers better, then that is fine.
but if my tool becomes popular and a megacorp uses it to promote their own commercial closed source features alongside it, then that's excessive. that's one reason i like the AGPL, it reduced that. but in my opinion the ideal license is one that limits the freedom to smaller companies. maybe less than 100 or 500 employees, or less than some reasonable amount of revenue. (10 million per year? is that to high or to low?)
and even for those above, i don't want revshare, just pay me something adequate.
It's not open source, because the definition of open source doesn't allow you to place any restrictions on who can use it or for what purpose. It's why licenses like "Don't use it for evil" or "Everyone except Anish Kapoor" aren't acceptable for a lot of Linux distros.
In practice your best bet is probably a license where everyone can use it, but which is incredibly hostile to use in a for-profit environment. Think AGPL, where you risk being forced to open source your entire unique-selling-point proprietary software stack.
some people are working on that, among others there is bruce perens: https://web.archive.org/web/20251206160538/https://perens.co... (sadly his site seems broken, the static files still work however: https://perens.com/static/DEVELOPMENT_LICENSE.txt )
FUTO is also exploring this space: https://sourcefirst.com/
It has always been like that, except we used to call it demos, sharewhare, beerware, postware,...
The free beer movement came out of UNIX culture, probably influenced by how originally AT&T wasn't able to profit from it.
Because the ratio of developers who do it for money to developers who do it for love of developing has dramatically increased, as computer science became a subject people studied for economic reasons, not just for fun.
Yeah, I think the paradigm has shifted. There's a perception that, while these companies have always profited off of our inputs, that we both benefitted. We contributed to a public good, they provided the platform, and profited off that platform.
Now it feels like the public good is being diminished (enshittification) as they keep turning the "profit" knob, trying to squeeze more and more marginal dollars from the good.
The system still requires the same inputs from us, but gives less back.
Yes, this 100x.
The MIT license didn’t require a lot of thought.