Remix.run Logo
fractorial 10 hours ago

> Do anti-LLM types expect to be vindicated in an orgy of copyright lawsuits that resets the industry back to 2022? What do people pushing expect to accomplish?

You weren’t kidding, huh.

m4tthumphrey 9 hours ago | parent | next [-]

I like the top reply:

> "The true purpose of AI is to allow wealth to access skill without allowing skill to access wealth."

rolandog 9 hours ago | parent | next [-]

Exactly; AI is to intellectual property or skills what shell corporations are to lobbying... they're a tool that won't benefit everyone equally and is unaffordable to most people.

It COULD be used for good (that's why its proponents use tone-deaf analogies comparing AI to seats on a rocket)... but we know that --- for the most part --- it WON'T be used for good... (It's already being used to spread more disinformation and to fan the flames of fascism).

Technically, you could argue that shell corporations could protect journalists, but you don't see journalists destabilizing democracies by fueling dark money to alt-right groups here and there.

ModernMech 7 hours ago | parent | next [-]

One of the very first things the government used it for when they got their hands on it was for targeting missiles, and then they promptly bombed a school full of kids. It's like Idiocracy meets Terminator.

esafak 22 minutes ago | parent [-]

Because the AI relied on outdated data; it was not a hallucination.

nh23423fefe 6 hours ago | parent | prev [-]

human repeats bad idea.

matheusmoreira 2 hours ago | parent | prev [-]

How many people have you all automated out of their jobs? None of you shed a single tear for them. Now that it's your turn, suddenly it's a problem?

overgard an hour ago | parent [-]

This is such a ridiculous take I hear all the time. The shitty ethics of some people do not represent the ethics of an entire profession. Most programmers are not automating people out of jobs. I've been professionally employed as a software developer for 20 years and I don't think a single thing I've ever written has ever replaced anyone's job. Hopefully sometimes it improves their job.

matheusmoreira 32 minutes ago | parent [-]

> don't think a single thing I've ever written has ever replaced anyone's job.

Doubt. Whatever it is your web app does, I bet corporations would have been forced to hire more people to do it for them, were it not for you.

And there's absolutely nothing "unethical" about it either. Toil is meant to be automated away. What I can't take is programmers thinking they're somehow above this.

The only crime here is stopping before AI replaces the CEOs and politicians. It should keep happening relentlessly until capitalism itself collapses and a post scarcity society is achieved.

prymitive 9 hours ago | parent | prev | next [-]

Is it "anti-LLM" or is it anti "here's some code I don't understand that a machine generated for me kthxbye"? Code is not just code, it's also liability and trust.

tossandthrow 9 hours ago | parent [-]

You literally spend 99.999% og your time blindly trusting code - and that is only because I assume ymthat you write code yourself.

For 99.999% of people, it is literally kthxbye on all code they execute on all their devices.

flohofwoe 9 hours ago | parent | next [-]

You sound like a webdev, e.g. the "let's just install 1000s of unvetted external dependencies" is nowhere else nearly as extreme as in web development land.

tossandthrow 8 hours ago | parent [-]

Please don't be personal.

flohofwoe 7 hours ago | parent [-]

> You literally spend 99.999% og your time blindly trusting code ...

Please don't be personal ;)

EvanAnderson 9 hours ago | parent | prev [-]

I don't think that's accurate. Until recently the code we rely on wasn't blindly trusted. People wrote and QA'd it. We may not have reviewed it personally, but that's one of the functions we outsource to software maintainers or "manufacturers".

I'm not "blindly trusting" code on my computing devices. I'm trusting the vendors / maintainers to do their job.

Until very recently the norm has been that the vast majority of code had human eyes and hands on it.

Edit:

The owners of those human eyes and hands had some type of accountability (either reputationally, in the case of free/open-source software, or occupationally, in the case of proprietary software).

The LLM has no accountability as to the output it generates.

The companies who make the LLMs also seem to have very little accountability, too. We've assumed a "blame the victim" stance when people use LLM-generated output in some inappropriate ways (legal briefs with "hallucinated" citations, articles "written" by LLMs). Whether that's the right location for accountability to be placed isn't for me to say, but that seems to be how it is.

I'm not sure that we're applying accountability to LLM-generated code in the same way we are for, say, the LLM-generated legal brief.

jadar 9 hours ago | parent | next [-]

A compiler is not an LLM, and I do not want to equivocate, but there are aspects of similarity. We do not assume people read the bytes of machine code to ensure it’s correct — there could be mistakes. We also write and run automated tests to ensure the code outputted from a compiler and an LLM behaves correctly. At some point, we won’t have to literally read every byte of code that comes out because we have a reasonable assurance that it’s correct.

EvanAnderson 9 hours ago | parent | next [-]

That we don't have to heavily scrutinize the code generated by compilers is a result of the huge amount of human toil that went into the compilers and test suites. Compilers are deterministic mechanisms so tests can be constructed.

LLMs, at least as they're currently constructed, aren't deterministic (the whole "temperature" thing). I don't see how to build a mechanistic test for something that has non-deterministic output. It feels a little bit like solving the halting problem.

I have no doubt we'll move away from human code review. The idea of large amounts of software edifice being built upon foundations that no human has reviewed or, perhaps even understands, is horrifying to me, though.

flohofwoe 8 hours ago | parent | prev [-]

Compilers also usually give you the same output for the same input. And fwiw I do spend quite a lot of time reading compiler output to check that it's not doing something stupid or unexpected (usually as part of optimization work).

Also this sort of 'technological whataboutism' really isn't helpful, compilers are entirely different from LLMs. I agree that it doesn't make much sense to read or review LLM output in detail, but I also don't plan to use LLM output for anything important or mission critical. That would be irresponsible.

AshamedCaptain 8 hours ago | parent | next [-]

In addition, when we usually say that triggering undefined behavior on C can start a game of Tetris or format your hard disk we're usually joking (or at least exaggerating), i.e. the most common failure conditions of compilers are really limited in scope, and very likely caught by whatever testing mechanism you use for the software.

No such limits for LLMs where losing all your files is about par for the course for everyone who uses them regularly.

pjmlp 4 hours ago | parent | prev [-]

JIT compilers certainly do not give the same machine code for the same input.

The actual machine code depends on several parameters, and it is very hard to replicate them, hence why many devs get benchmarks with JITs wrong.

Additionally, compiler optimisation passes with machine learning is starting to be a thing, yet another way how the machine code differs for the same input across compiler executions.

tossandthrow 9 hours ago | parent | prev [-]

> Until very recently the norm has been that the vast majority of code had human eyes and hands on it.

What quality does it have that humans had eyes on code?

Elite teams likely still produce code of better quality with a higher qa bar than agentic code. But that category is dimishing everyday.

The core point is that so much trust is reduced to "Joe in cubicle". Also a lot more than what he can carry.

Most of the code that is being executed on your behalf is far from written by elite teams.

flohofwoe 9 hours ago | parent | next [-]

It has nothing to do with 'elite teams', it has to do with decades long and very careful maintenance.

It's too early to say whether LLM generated projects will ever reach that sort of maturity, most examples I've seen so far are basically "fire and forget". But lets talk again in one or two decades, maybe there will be counterexamples of successful open source projects which will be just as well llm-maintained as human-mainained.

But I suspect that to reach that sort of maturity, the resulting human effort will be mostly the same (e.g. not much of a productity win - except maybe on the 'edges', e.g. maintaining the test suite, documentation, helping to analyze bugs..., e.g. these are examples where LLMs are genuinely useful and where plagiarism hardly matters).

tossandthrow 8 hours ago | parent [-]

It really is not.

There are some areas that are critical and where software developers carefully will detail stear the work.

But the vast amount of software written, react components and rest endpoints, are very ripe to be entirely written by agents.

flohofwoe 7 hours ago | parent [-]

> But the vast amount of software written, react components and rest endpoints, are very ripe to be entirely written by agents.

In that I agree, nobody should be forced to write React code manually, that's almost a human rights violation ;)

REST endpoints (and the code talking to those endpoints) should be code generated anyway though, no need for LLMs, and instead of human language prompting, a precise IDL should be the spec and basis for a mechnical code generation process. That problem was solved decades ago with much more pedestrian technology.

E.g. it basically comes down to "it's fine to use LLMs for software that shouldn't have been written in the first place", and funny enough that's where LLMs are really good at: creating software that has been written a million times before with only minor variations, and doing this type of work manually (cranking out one cookie cutter React webpage or REST API after another) is essentially what's called 'bullshit jobs' (which bring food on the table though, but that's another topic).

PS:

> and where software developers carefully will detail stear the work.

...I think the further a project evolves, the less this "detailed stearing" will be any more productive than doing the same without LLMs. The older a project, the more the work shifts from implementation to decision making, and in most cases the result of that decision is just a very tiny code change. I already see cases in my daily work when I use 'agentic workflows' where a tiny change takes longer and involves more 'collatoral updates' then just fixing that one frigging line of code by hand like in the olden days, and for LLM-generated code bases I really do prefer to not mix LLM and manual work, I think that's the worst of all options.

EvanAnderson 8 hours ago | parent | prev [-]

> What quality does it have that humans had eyes on code?

The human who had their eyes and hands on the code has accountability.

I think how accountability is going to work, in the case of LLM-generated code, is still an open question.

(I dropped-on an edit to the parent comment to this effect, too.)

tossandthrow 8 hours ago | parent [-]

> The human who had their eyes and hands on the code has accountability.

They are not.

You can not go go back to a laid off person / one who quit and keep them accountable.

So this is absolutely not the case.

Devs are not accountable for their code.

EvanAnderson 8 hours ago | parent [-]

You're being reductive or just obtuse.

The company that employed the developer ultimately holds the accountability in the marketplace. The employed developer maintains (or loses) their job because of their accountability to their code (or, at least, they should). There's an economic incentive for all parties involved.

In the free/open-source world the incentives aren't economic, but they're still there.

tossandthrow 7 hours ago | parent [-]

> You're being reductive or just obtuse.

> or, at least, they should

Seems like you are the obtuse one here, and you appear to know it.

EvanAnderson 7 hours ago | parent [-]

I don't get how saying companies should hold their employees accountable, which doesn't always happen, is somehow obtuse.

I give up. I feel like you're a robot designed to waste my time.

tossandthrow 6 hours ago | parent [-]

Fair enough, that's on you.

You are talking from an ideal point of view. You want the companies to hold employees responsible.

But that is is not how it work. Why you appear obtuse.

Eg. Look at th3 therac25 case. No developers was held accountable.

We have spend more than a decade remove accountability from indiviauls. Using limited liability, insurance, and workers protection.

Accountability is the last reason why we need humans over agents.

EvanAnderson 3 hours ago | parent [-]

Sorry for the exasperation.

At the start of this you said: "For 99.999% of people, it is literally kthxbye on all code they execute on all their devices."

I think that's inaccurate. The vast majority of code running on "all their devices" is code made by employees of companies being held accountable through traditional industry methods, or free.open source projects where reputational integrity was at stake. Those developers have been held accountable, for some value of accountable.

Maybe there's less value in human accountability than I think there is. Only time will tell. That's a different conversation.

The code running "for 99.999% of people" is not "literally kthxbye" LLM-generated code without someone behind it holding accountability. Maybe it will be in the future, but it's not now.

randusername 10 hours ago | parent | prev | next [-]

The GCC stance seems reasonable to me, where do we think the rage is coming from in comments like this?

Off the cuff, I would be surprised if the GNU project embraced AI, so I'm confused that people think so strongly otherwise.

account42 9 hours ago | parent | next [-]

There seem to be a set of people who treat AI as religion which then makes anything opposing it (even mildly) into heresy.

cozzyd 9 hours ago | parent [-]

Or they're self conscious about their use of AI so they take a maximalist stance to compensate.

olalonde 8 hours ago | parent | prev | next [-]

Can't speak for others but I'm just tired of hearing far-fetched copyright concerns that mask the real motivation (ideological opposition to LLMs).

overgard 44 minutes ago | parent | next [-]

I don't think the concerns are far fetched at all. Look at how image models spit out copyrighted stuff all the time. Midjourney has a bizarre EULA clause that if you use it to generate images that violate copyright and _they_ get sued, they can hold you liable downstream. Which is wild to me -- just don't train on things you don't own and this is not a problem!

In images it's much more _obvious_, but I think code is very likely to have similar problems. Like, websites that an LLM spits out are often very very similar. It wouldn't be shocking to me if some of the code in the training set was trained off GPL code, and there are small GPL violations all over the place.

graemep an hour ago | parent | prev | next [-]

The stance may be reasonable, but the reasoning is not clear to me and the limit does sesm to suggest copyright concerns that are, as you say, far fetched.

leonidasv 8 hours ago | parent | prev | next [-]

They still allow LLM-generated code for tests, LLM-assisted debugging, bug discovery and code reviews. It doesn't seem so.

olalonde 7 hours ago | parent [-]

At the same time, they would be somewhat forced to concede those use cases if they wanted to stick to the copyright story. Maybe you're right but I remain skeptical.

amusingimpala75 an hour ago | parent [-]

Yes but if the concern is being forced to remove code in the case of copyright violation it is trivial to remove code that is a test case as opposed to a feature of the compiler

randusername 8 hours ago | parent | prev [-]

It's far-fetched that the GNU project is authentically concerned about software licensing?

olalonde 6 hours ago | parent [-]

No, it's far-fetched to believe GCC would get sued for incorporating LLM-generated code.

overgard 41 minutes ago | parent | next [-]

The risk might be small -- but is it a risk they need to take at all? We're talking about a very mature project here that more or less needs to move at the speed of standards bodies, which is basically glacial. Being the first to implement C++ 29 probably isn't that big of a deal. People do not upgrade their compilers daily, shit, most projects stay on the same version for years, so optimizing for velocity seems like a bad idea here.

Ekaros 2 hours ago | parent | prev | next [-]

Yeah, I would question that part. On other hand I would not as them risk being able to sue worth it. Which use of LLMs could very well result in.

gspr an hour ago | parent | prev | next [-]

I think you know that well-known, highly visible entities usually set their legal bar a bit higher than "I'm sure we won't be sued over this".

an hour ago | parent | prev [-]
[deleted]
mrgoldenbrown 8 hours ago | parent | prev | next [-]

If the only way you know how to code is via LLM, it makes sense you would get defensive/ragey when someone discourages it.

user43928 9 hours ago | parent | prev [-]

At face value a policy that essentially prohibits AI generated implementation seems entirely unreasonable to me.

natebc 8 hours ago | parent [-]

I guess that's where the rage comes from. People that believe a policy is without reason.

user43928 7 hours ago | parent [-]

I said at face value because there was no reason given in either the policy nor the article submitted here.

It would be interesting to know why they decided for a general prohibition, rather than going with the default "a human must be responsible for the contribution" kind of policy.

Perhaps they have received a flood of undesirable AI generated contributions, and actual contributors do not use AI significantly.

olalonde 10 hours ago | parent | prev | next [-]

He's correct though. You would need 3 extremely low probability events to all occur simultaneously for the concern to actually manifest.

1) Courts reverse their previous decisions and declare LLM generated code as belonging to LLM labs.

2) LLM labs decide to assert their copyright and sue open source projects.

3) They are able to prove that the code was generated by an LLM and not just any LLM but their LLM.

tsimionescu 9 hours ago | parent | next [-]

The concern related to copyright is not that the AI labs would assert copyright over the code produced by their LLMs - that is a complete strawman.

The concern instead is that LLMs and all of their outputs may be found to be derivative works of their entire training set, and thus rendered unusable (as the training set is not distirbutable under any license).

I think this ship has long sailed and no court is going to dare give such a decision given the money involved, for better or for worse. But it's a much more realistic scenario, in principle, than LLM labs going mad and attacking their own customers.

Edit to add: there is another, completely different, copyright risk associated with LLMs - and one that is much more realistic. It is the fact that code generated by LLMs may not, in fact, be copyrightable at all. Which would mean that it can't be subject to the GPL. As long as it remains a minority of GCC code, this wouldn't matter much, but it could in time lead to significant portions of GCC becoming public domain, and thus cooyable, modifiable, and redistrubutable without providing the four freedoms.

7e 3 hours ago | parent [-]

In many timelines, non-copyrightable code in GPL project doesn’t restrict the user’s freedom, since an LLM can easily reimplement the functionality clean-room. AI has brought levels of freedom to users that GNU could never do. Practical levels of freedom, leading to real, positive outcomes. Software is finally free in the real world.

gspr an hour ago | parent [-]

Cleanroom?! What the hell kind of definition of a cleanroom is it when you get to take hundreds of GB of compressed code with you into it?!

Retr0id 10 hours ago | parent | prev | next [-]

Isn't there also a concern that an LLM may reproduce copyrighted code verbatim (or close enough), and the original author asserts their copyright?

jmull 9 hours ago | parent | next [-]

Not to mention the moral concern.

IP law (like a lot of other things) has been skewed toward the interests of business, even when that conflicts with fairness or societal good. For all its flaws (IMO), the free software movement tends to be principled. Just because something is legal doesn’t mean it’s right.

justthehuman 10 hours ago | parent | prev | next [-]

+1, I also thought this was the actual concern.

panzi 9 hours ago | parent | prev | next [-]

Not just when it reproduces code. Since fair use doesn't exist like that in a lot of countries the question is if the training itself is a violation. Are there e.g. EU or Japanese rulings on that?

worthless-trash 9 hours ago | parent | prev | next [-]

I had early chatGPT spit my own erlang code back at me WITH my comments.

user43928 9 hours ago | parent | prev | next [-]

To my knowledge there is not a single known case where this happened.

News back then were about intentionally prompting to output known copyrighted material.

The parent comment still stands in my opinion:

When, despite millions of developers using agentic AI already, are these lawsuits supposed to manifest?

dijksterhuis 9 hours ago | parent | next [-]

> To my knowledge there is not a single known case where this happened.

> News back then were about intentionally prompting to output known copyrighted material.

First, there are other cases if you take the time to dig. This is quite an old example (GPT-2) as i haven't kept up to date on this field recently, but it does show that this problem has been known about since before these systems were widely adopted: https://arxiv.org/abs/2012.07805 [0]

Second, GP said nothing about the type of effort required to make it happen, just that it can be done and that the copyright owner could come along and cause legal problems later. It's absolutely possible to have a fly-by contributor who purposefully asks for code that reproduces X/Y/Z without a maintainer knowing about it.

But then the maintainer is the one in legal trouble.

> When, despite millions of developers using agentic AI already, are these lawsuits supposed to manifest?

Legal / copyright / etc. cases often take a lot longer than a couple of years to come to fruition.

---

[0]: edit -- to clarify this is an example of the reproduction problem, not an example copyright infringement case.

user43928 9 hours ago | parent | next [-]

The problem you linked is an older example of intentional prompting for copyrighted material.

The concern discussed here is copyrighted material being generated unintentionally and the original author asserting their rights.

This has, to my knowledge, not happened once.

If we are not talking about unintentional violations, I don't understand the point of the discussion.

I can also intentionally copy paste the copyrighted material into my merge request without the use of AI in an attempt to get the maintainer into trouble.

dijksterhuis 9 hours ago | parent [-]

> The concern discussed here is copyrighted material being generated unintentionally and the original author asserting their rights.

both intentional (malicious contributor) or unintentional (Large-Laundering-Model) are copyright issues -- which is the point of GCC's policy.

> I can also intentionally copy paste the copyrighted material into my merge request without the use of AI in an attempt to get the maintainer into trouble.

You can. You can also do it significantly faster with significantly less effort while being harder to detect using agents etc.

user43928 8 hours ago | parent [-]

I do not think some untested theory about sabotaging open-source projects by intentionally inserting copyrighted material using AI, causing legal issues for maintainers, is worthwhile to discuss here.

That is obviously not what anyone was referring to, nor does it make sense, when there is a much more reasonable basis to prohibit the same contribution.

Namely inserting vulnerabilities. This one actually happened before afaik, and provides a clear benefit to the attacker.

olalonde 9 hours ago | parent | prev [-]

> just that it can be done and that the copyright owner could come along and cause legal problems later. It's absolutely possible to have a fly-by contributor who purposefully asks for code that reproduces X/Y/Z without a maintainer knowing about it.

If a contributor doesn't care about submitting copyrighted code, they can do it without an LLM as well.

dijksterhuis 8 hours ago | parent [-]

They could, but an LLM makes it faster and easier to launder code. And makes it harder to detect.

Plenty of github accounts now are agent-driven monstrosities just trying to inflate someone's contribution stats etc.

jryan49 9 hours ago | parent | prev [-]

I mean ai has generated copyright headers verbatim in code I asked it to make. I had a tutorial open from the web and asked the AI to generate an example for me and it was the example from the tutorial verbatim as well...

user43928 9 hours ago | parent [-]

This never happened to me and there is not a single such occurrence in my main project, across 150k LOC.

I would be surprised if a frontier model generated unexpected copyright headers during typical usage.

jryan49 8 hours ago | parent | next [-]

It was a frontier model from a few months ago. It hasn't done it recently. But it has happened. I imagine if there isn't a lot of training data for an idea it probably has a higher change of generating verbatim, so as time goes on, it should become less of a problem (at least with high quality models).

nemomarx 9 hours ago | parent | prev [-]

the people blindly submitting prs are not going to be using expensive frontier models, though.

agentultra 9 hours ago | parent | prev | next [-]

That would be an example of, “overfitting.” It is something the AI labs are concerned about. They tweak parameters to try and avoid it.

It’s a hard balancing act to do. Give in too much randomness and you get non-sensical outputs that are difficult to align. Fit too closely to the training data and the model regurgitates the training data.

And oh, what’s that copyrighted material we never made any agreement to use doing in there?

olalonde 9 hours ago | parent | prev | next [-]

This doesn't really happen by accident, especially where it's significant enough to constitute copyright infringement. And to my knowledge, there hasn't been a single lawsuit over this in the entire history of LLM-assisted coding.

dijksterhuis 9 hours ago | parent [-]

> there hasn't been a single lawsuit over this in the entire history of LLM-assisted coding.

the "entire history of" is circa 3-4 years, which is very much a tiny period of time compared to normal legal system / copyright law stuff (IANAL).

olalonde 9 hours ago | parent [-]

It's enough to tell you that, if it does happen, it must be quite rare and not a widespread systemic issue. It's also worth noting that Anthropic and co are so confident that it's a non-issue that they offer full copyright indemnification to their commercial users.

dijksterhuis 8 hours ago | parent [-]

> It's enough to tell you that, if it does happen, it must be quite rare and not a systematic issue.

alternative perspective: it's just taking time for the lawyers to figure out what they can sue them for.

olalonde 8 hours ago | parent [-]

Not sure I understand. If some company or open source project is violating your copyright, you sue them for copyright infringement, no?

bluGill 9 hours ago | parent | prev [-]

There is concern, but the more I think about it, the less convinced I am. LLMs might produce a snippet, but copyright requires more than that. Last I checked (I'm not a lawyer, this was far enough back that the law has had major changes, and different countries have different laws! - read this with plenty of salt) if you start with copyright work and replace all but 10% that final amount just disappears since there isn't enough original to claim copyright anymore. You can never claim copyright over 'printf("Hello World");' - it is too generic. Most of what I've seen an LLM produce is likewise generic enough that even if it is a copy, it wouldn't be a copyrightable snippet.

dijksterhuis 9 hours ago | parent [-]

reminded me of:

> The complaint argued that "the basis of the Gaye defendants' claims is that "Blurred Lines" and "Got To Give It Up" "feel" or "sound" the same. Being reminiscent of a "sound" is not copyright infringement. The intent in producing "Blurred Lines" was to evoke an era. In reality, the Gaye defendants are claiming ownership of an entire genre, as opposed to a specific work"

they lost (eventually) https://en.wikipedia.org/wiki/Pharrell_Williams_v._Bridgepor...

wider point -- whether or not a copy is a copy and whether it is is infringing on copyright or not ultimately has to be decided by a court case when it's not an obvious and clear cut violation. especially in the USA with the utterly mental fair use law.

luke5441 9 hours ago | parent | prev | next [-]

No?

1) Someone re-licenses GCC under a non-GPL license.

2) EFF sues them, to stop the behaviour

3) Court tells EFF that they have no standing to sue because LLM generated content has no copyright

Obviously this happening would be in the future after someone translated GCC to Rust with LLMs or something.

olalonde 9 hours ago | parent | next [-]

Again, it would require an extremely unlikely set of circumstances.

1) All of GCC would have to be LLM generated. If some parts are not, it's sufficient to prevent the re-licensing.

2) That someone would have to prove that all the GCC code was in fact LLM generated. Good luck doing that.

3) A court would have to decide that all the LLM-generated code does in fact fall under public domain, because it involved insufficient human input.

skeledrew 9 hours ago | parent | prev [-]

> Someone re-licenses GCC under a non-GPL license.

A pointless act since code is now free. The GPL exists to ensure code freedom in an era when code was expensive. Yes I'm aware that the meaning of "free" is a bit conflated here, but the point stands.

sodapopcan 8 hours ago | parent | prev [-]

> He's correct though.

He's correct but it's an irrelevant argument, he's simply making an emotional, and very childish, attack on someone because they don't like the tech he likes. Banning LLMs in your project, regardless of the reason, does not mean you think they are ever going to go away, or even that you want them to.

TZubiri 31 minutes ago | parent | prev | next [-]

Isn't that a possibility? Is anyone expecting case law to evolve and adapt instantly? To say nothing of new laws.

10 hours ago | parent | prev | next [-]
[deleted]
freakynit 10 hours ago | parent | prev [-]

You are absolutely right.