| ▲ | rpdillon 18 hours ago |
| > If you want to gatekeep or only create stuff to boost your own ego or portfolio, then AI might be an issue, if you actually want to build stuff, AI is godsend. Exactly this. I've been very confused by the free software advocates that seemed to hate AI until I realized their reasons for releasing software under an open source license were very different than what I assumed they were. |
|
| ▲ | wiz21c 18 hours ago | parent | next [-] |
| I release my code as free software for two reasons: 1. The credits for my code are protected (with the GPL you have to tell where your code originates from). That's the ego part. It's important to me because I'm not paid for my software. So credits are an important reward. 2. I want people to think twice about reusing my code. I use the GPL license because I think sharing software is the ultimate goal. So I force people to share my software by using the GPL. That may sound "extreme" (that's the whole open source vs free software debate) but, not being a full time politician, I can't change laws to push society in the direction I want. At my level, that "push" is the GPL choice. Maybe it's not noble enough, maybe it's cowardice, but it's my way (compare that with those who simply don't care). AI severely weakens both of these. And for people like me, this forces us to reconsider our position. For my part, I accept the legal point of view that A.I. doesn't steal code, and just reproduces the ideas in the code. So, as far as ideas can flow in society, I'm OK with that (that's the principle behind copyright laws). If AI has its way, one day one will not need to write software, we'll just ask the AI. In that case, software will be dead and free software will die with it too. By then I'll do my "local politics" another way and follow the next RMS. |
| |
| ▲ | jcelerier 17 hours ago | parent | next [-] | | > The credits for my code are protected (with the GPL you have to tell where your code originates from) But that's literally anathema to the spirit of GPL. Copyleft exists only as a reaction to copyright which is sadly ingrained in legal systems, but the original thought about free software, at the time of GPL inception, is that in an ideal world, copyright shouldn't exist for software ; it's leveraged by GPL only to protect against abuse of copyright holders that could close open code, which is thus made impossible "legally" with the GPL. AI makes this distinction fal into "practically" as pretty much anything is "open" for individual use now (e.g the only use that matters). https://www.gnu.org/philosophy/fsfs/rms-essays.pdf | | |
| ▲ | bonzini 17 hours ago | parent | next [-] | | Attribution and copyright are separate. Who says that, even if copyright didn't exist for software, attribution also wouldn't? If anything, the remark that I have to make to the parent is that in principle attribution is also required by non-copyleft licenses. However, I doubt it's respected for the hundreds of crates or npm modules in a typical Rust or JavaScript project... | |
| ▲ | mitxela 16 hours ago | parent | prev | next [-] | | Even the true copyright abolitionists (who want companies like Oracle to be able to fork their software and make a billion dollars releasing the binaries) still use MIT license which requires attribution. | | |
| ▲ | ndriscoll 14 hours ago | parent [-] | | I'm a copyright abolitionist, but I think Oracle should be required to release the source code with their binaries as a basic consumer protection. I also don't care about attribution. |
| |
| ▲ | za_creature 17 hours ago | parent | prev [-] | | The spirit of free software is about learning from others and having control of your hardware. Given the supposed commoditization of intelligence and recent memory prices, I'd say LLMs are literally anathema to the spirit of the GPL. | | |
| ▲ | intrasight 17 hours ago | parent [-] | | I don't think "you own your own hardware" will be true for long. Spirits don't get much legal protection. | | |
| ▲ | mitxela 16 hours ago | parent | next [-] | | If LLMs are as good at RE as everyone says, we will own our hardware again. | | |
| ▲ | intrasight 16 hours ago | parent [-] | | You'd have to build your own fab from ground up - meaning no ASML. Is not going to happen. | | |
| ▲ | mitxela 14 hours ago | parent [-] | | You don't have to own the entire pipeline to own enough of it. People run Linux and say they own their OS. |
|
| |
| ▲ | za_creature 16 hours ago | parent | prev [-] | | They used to. We used to call those spirits "rights". |
|
|
| |
| ▲ | za_creature 18 hours ago | parent | prev | next [-] | | > A.I. doesn't steal code, and just reproduces the ideas in the code Then they don't need to train on github, no? Why not release a new model trained from Knuth's Art of Programming, Cormen's Introduction to Algorithms and the C specification. Feel free to throw in any other published literature related to STEM, but stick to the code samples from the books. I'm certain it'll be able to change the color of a CSS button, right? | | |
| ▲ | kolinko 17 hours ago | parent | next [-] | | What you said doesn't disagree with what the parent said. LLM can be trained on a code and at the same time reproduce the core ideas. That's what LLMs do after all - they convert the training data into their own internal models and representations, and then reproduce the ideas. Sure, some things/patterns, that were repeated multiple times, LLMs will tend to repeat verbatim as well, but that's not that big of a problem. As a person who invented a few algorithms on my own I absolutely love LLMs and I don't mind them being trained on my work, but yeah - I've been way less likely to publish open source over the last year. In the past, if some of my stuff got traction, the credit was close to automatic (early adopters credited or at least knew where they got it from). Nowadays, LLMs will train on these ideas, rewrite them, and give no credit. Still, I prefer this to having no LLMs at all. > but stick to the code samples from the books.
> I'm certain it'll be able to change the color of a CSS button, right? A good enough LLM will just decompile a browser, figure out CSS spec from it, and yes - figure out how to change the color of a CSS button from first principles. There is no point to do this with CSS, but with other things it's now easier to just dig through sorces or direct bytecode than to bother checking docs. | | |
| ▲ | za_creature 17 hours ago | parent [-] | | Same argument, just one level down. Can it decompile a browser using a specification of x86 and the source code of the compiler? e.g. without training on the source code and binaries of all software it was able to rip from the internet? |
| |
| ▲ | ben_w 17 hours ago | parent | prev | next [-] | | > Then they don't need to train on github, no? Why not release a new model trained from Knuth's Art of Programming, Cormen's Introduction to Algorithms and the C specification. Because they're really really stupid and only make up for this by being really really stupid really really fast. This has been ruled, by actual courts, to not be "stealing" (not even in the "you wouldn't steal a car, piracy is theft" sense that film and music studios campaigned on). The last I heard was the "Chinchilla" scaling law was ~20 training tokens per parameter. Humans are, if you'll excuse a very hand-waving Fermi estimate, 100,000 times more data-efficient at learning stuff (it's really hard to tell given we're visual creatures that happen to speak, while LLMs are text-based things that happen to see). | | | |
| ▲ | Pannoniae 17 hours ago | parent | prev | next [-] | | To be fair, you also don't restrict yourself to those texts either. You read news, you use other programs, you look at websites and so on. And while the norms vary per field, things aren't really reinvented from scratch. The standard FPS controls aren't reinvented for every shooter game. The standard website layouts aren't reinvented for every website. The standard command line behaviour isn't reinvented for every CLI program and so on. | | |
| ▲ | za_creature 17 hours ago | parent [-] | | Those were all included in "published literature relating to STEM". Just skip the source code. Consider it an easier challenge than reinventing relativity from 19th century physics. | | |
| ▲ | Pannoniae 17 hours ago | parent [-] | | But software isn't like traditional academia. It might have grown from it but most advances aren't really published in the traditional sense, you've got blogposts, presentations and source code instead. This would be like teaching cooking without looking at any recipes, just from physics and first principles. Or learning music without looking at the sheet music / listening to any existing songs, just generic musical theory and chords. I don't think humans can do it "zero-shot" either... | | |
| ▲ | za_creature 16 hours ago | parent [-] | | > advances aren't really published https://dl.acm.org/ | | |
| ▲ | Pannoniae 16 hours ago | parent [-] | | I don't see how this disproves my point. There's a vast divide between "theoretical" and "applied" software engineering. You don't usually see Google engineers publish their search optimisations in journals. And similarly, you don't see university professors making commercial libraries from their articles' ideas. This isn't the case in every field but in software, it very much is. And this implies that training on the "theoretical" side of things doesn't give you much insight on the "practical" side. Stuff like cyclomatic complexity, UML diagrams and all that stuff might be well-represented in literature but way less so in real software, so training on the literature will produce completely different software than training on production software code. | | |
|
|
|
| |
| ▲ | ThrowawayR2 13 hours ago | parent | prev | next [-] | | > "Why not release a new model trained from Knuth's Art of Programming, Cormen's Introduction to Algorithms and the C specification." What makes you think that wouldn't work? I think a lot of the hype around AI is vastly overblown but that seems to be well within the scope of what they can be expanded to do in the not too distant future. AlphaGo was trained through self-play reinforcement learning IIRC and I don't really see a reason that some sort of equivalent couldn't be done for generating code starting with textbooks and access to a Linux CLI as a reference. It would be an interesting experiment at least. | |
| ▲ | jazzypants 17 hours ago | parent | prev [-] | | I'm sorry, but what are you trying to say here? There are books that teach you how to change the color of a CSS button... |
| |
| ▲ | rpdillon 18 hours ago | parent | prev [-] | | You say that sharing the software is the ultimate goal, but you're using that argument to justify not sharing your software. That's hard for me to understand. I also don't think that just because you have to ask AI to write the software, free software will die. Because people don't understand their own requirements, I don't think we're going to get to a place where AI can one-shot, even moderately complex software, and so creating software will continue to be some effort. I fully expect that the norm will become that we give away free software and expect other people to pick it up and tune it to their own needs with their AI. But that doesn't mean that free software is dead. It means it evolves. | | |
| ▲ | kolinko 17 hours ago | parent [-] | | What do you consider "moderately complex software"? | | |
| ▲ | rpdillon 16 hours ago | parent [-] | | Something where the person that is going to be using it can't easily define the full set of requirements in one go because they're going to need to interact with it first, and subsequent requirements will emerge after use. The limitation in this case will not be the AI's ability to implement what was requested. It will be the human's ability to articulate what success looks like. |
|
|
|
|
| ▲ | za_creature 18 hours ago | parent | prev | next [-] |
| While Stallman may have been originally upset about his printer, the primary motivation behind open source software is: Nothing up my sleeve. This of course requires audit and that requires that the code is written for human consumption, otherwise nobody will bother. Sure you can vibe a printer driver but how sure are you that your LLM didn't include a backdoor in the millions line of slop? |
| |
| ▲ | williamcotton 18 hours ago | parent | next [-] | | How sure are you that any printer driver didn’t include a backdoor? What’s the difference between the LLM code with the backdoor and the human code with the backdoor? | | |
| ▲ | za_creature 17 hours ago | parent [-] | | The ability to audit the code. If not that, the ability to trust the reputation of the author which creates an incentive not to willingly insert a backdoor. Yes, `npm install` was always bullshit because most people didn't bother to check, which is exactly why it was exploited multiple times, which created a conversation about "supply chain security". If you want to argue that "npm changed the world" then you are correct. It did not change the world for the better though. | | |
| ▲ | williamcotton 17 hours ago | parent [-] | | Why is LLM code always harder to audit? So LLMs might decide to add backdoors without prompting? | | |
| ▲ | za_creature 17 hours ago | parent [-] | | I'm less worried about what LLMs decide and more about what their system prompts tell them to do. |
|
|
| |
| ▲ | rpdillon 17 hours ago | parent | prev | next [-] | | Trusting software produced by others is not a new problem; I consider AI to be a tool, and so my techniques for establishing trust are the same as they have always been. I look at the person wielding the tool. | | |
| ▲ | ben_w 17 hours ago | parent | next [-] | | > I look at the person wielding the tool. I look at the whole chain of influence behind them, and it's quite a lot more upsetting than the smiling face I interact with. The whole "AI is a Lovecraftian tentacle monster wearing a smiley face" thing applies to simple bureaucracies (replace Lovecraft with Kafka), to corporations (replace Lovecraft with IDK, most anarchists?), and governments (Orwell?) Tools made by tools made by tools, along more steps than most people know even when their job is one of them. Somewhere there's a kid working a dangerous mine without the right safety equipment, elsewhere there's a sweatshop, another place a "reeducation camp". But who do I see? A cashier, mostly. Someone whose job involves smiling to customers even when we're idiots. | | |
| ▲ | rpdillon 16 hours ago | parent [-] | | I'm not sure what point you're trying to make. I put trust in individual people, not organizations. You seem to be making a point about supply chains, but I'm not sure how it relates to the point about trust. You seem to be making a different point about some kind of exploitation. | | |
| ▲ | ben_w 14 hours ago | parent [-] | | Almost everything I interact with was made by an organisation (or a disorganisation), not by an individual. Say I download an app. Who made it? The programmer? Their PM? Apple's store requirements? The US government, for whom there was a special tickbox I had to agree to last time I uploaded an app? Trust is for the mechanic, driver, builder; but for 90% of my interactions I have to trust my government set good rules and other people followed them. I can't do this with AI, neither good rules nor them being followed, but I also can't do it when the OS company and app devs are foreign, as they generally are to me now. |
|
| |
| ▲ | za_creature 17 hours ago | parent | prev [-] | | Then you best hope that person has read https://people.cs.umass.edu/~emery/classes/cmpsci691st/readi... |
| |
| ▲ | mitxela 16 hours ago | parent | prev [-] | | That's a motivation for source available. You can have commercial copyrighted software that's NUMS. You can deliver the customer source code (slightly customized for traitor-telling of course) and tell them to do what they want but never share it. grsecurity even managed this with GPL software! |
|
|
| ▲ | intended 16 hours ago | parent | prev | next [-] |
| Drive by code dumps from people who have "democratized Natural Language code" which pushes all the work of verifying whether it works on the few active maintainers is hell. Any collective group with open contribution will end up hating it. Why is this a surprise? |
|
| ▲ | matsemann 18 hours ago | parent | prev [-] |
| Exactly not this. Way to straw man all counter arguments before they even got any. |
| |
| ▲ | rpdillon 17 hours ago | parent [-] | | I haven't heard any coherent arguments other than getting credit and building a portfolio. Are there others? | | |
| ▲ | matsemann 16 hours ago | parent | next [-] | | I'd wager 99 % of the OSS the world runs on is people that never have cared about credit or building a portfolio. What they do want, however, is to not have to spend time on the thousands of AI generated pull requests and bug reports. | | |
| ▲ | rpdillon 16 hours ago | parent [-] | | Completely agree that low-value pull requests and bug reports are a problem, but that's not a problem with AI. That's a problem with people using GitHub and trying to do collaborative development in an ungated environment. Free software and open source are orthogonal to collaborative development, as we see with projects like SQLite, or AOSP, or Java, each of which impose their own gates for contribution, separate from the ability to generate code. | | |
| ▲ | matsemann 16 hours ago | parent [-] | | Sorry, but this seems like just moving the goalpost. | | |
| ▲ | rpdillon 15 hours ago | parent [-] | | I said people wanted credit more often than I had expected. You said "Way to straw man all counter arguments before they even got any." The current point you're making is (I think) that OSS devs don't want credit, they want to be free of spam. I, for example, host my free software on fossil and don't accept contributions at all. It's not that I don't want them, it's that I don't want the noise, so I feel like that's a valid way to distribute open source. But when I raise that, you're saying I'm moving the goalpost. I think the goalpost is in the same exact location as it has been for the entire discussion: open source authors that don't care about getting credit and want to distribute their free software can do so without any worry about AI. If your underlying point is that AI has lowered the barrier to entry for code submissions, making previously-viable approaches to collaborative development infeasible, that's completely fair, I just wasn't treating that as fundamental to open source development in the same way you were. |
|
|
| |
| ▲ | watwut 17 hours ago | parent | prev | next [-] | | Neither of your guesses is reality based. Open source contributors get no credit in general. To the point that even commenters on HN dont seem to know who they, in general are. That being said there is absolutely nothing wrong with building a portfolio. It is 100% valid motivation. The only issue with that theory is that no one cares about your open source contributions. Not employers, not peers, no one. What I do find fascinating tho is that fans of the most selfish egoistical companies and tech groups ... insinuate artists, open source programmers, writers or anyone else is selfish or otherwise disapponting if any part of their work involve actual human motivation. | | |
| ▲ | rpdillon 16 hours ago | parent [-] | | I wouldn't say that wanting to contribute to a shared commons of cool stuff isn't a human motivation. And I'm not deriding those that build open source to boost their own reputation. I'm just much less interested in their work than the work of folks that are motivated by improving the commons (even if they get no credit). | | |
| ▲ | watwut 9 hours ago | parent [-] | | You are imagining people in your head. Most serious open source contributions are paid for. Per FSF survey overwhelmingly so. Because, they are a lot of work. They are not hobbies or kitchen soup two hours a week effort. These require a lot of sustained effort and time, that would either takes time from your paid job, or would make you effectively work 60 hours a week which means you have no other life. End result is that these are paid positions, so. |
|
| |
| ▲ | sriram_malhar 17 hours ago | parent | prev [-] | | Why do we need more? Why is that not a big enough reason. If a modern-day Beethoven were told that his work will be slurped in by a machine and he will remain unknown to the world, would it be acceptable to him? To you? | | |
| ▲ | rpdillon 16 hours ago | parent [-] | | Context: I was accused of raising a strawman argument. I was explaining that I don't think it's a strawman, and your comment suggests you agree. It's a perfectly good reason, but I lament the loss of people who are doing open source just to get credit much less than I would lament the loss of people doing open source because they wanted to contribute to a shared commons. Fame only has utility so long as it gets you paid. If you can get paid without being famous, that's probably a win. I'm not very concerned about unrecognized genius: they are all around us, and the usual rule is that we've never heard of them. I think the that's just fine. |
|
|
|