Hacker News Reader

Comment by kmeisthax | Hacker News Reader

Right. And furthermore, I don't actually think prompts alone are copyrightable in most cases - I just wanted to propose an argumentum ad absurdum. Certainly, you can't argue creativity when you're also keyword-stuffing your prompts to call up various feature sets that the model just so happens to associate with them.

View on HN

The output of a compiler (i.e. A translation program) is created via a prompt (the source code). The output object code is very much copyrighted. People keyword stuff their source code all the time (pragmas) in order to influence the generated output. Why does that object code deserve copyright protection except when the compiler is an AI model (i.e. A translation program)? Compilers use genetic algorithms and weights from profiling in order to generate better output. Where does the output stop being capable of copyright protection because it's no longer "creative"?

If a museum can include a small portion of a frame around a public domain painting and claim new copyright as a result - surely any smallest spark or creative influence qualifies, including choosing a single word and choosing the model and time and which output is selected does as well.

The idea of work for hire, and the notion of copyright assignment, applies to people and not machines or processes employed in the creation of a work. Your brush manufacturer would never dare try to claim that their creative selection of fibres and thus their contribution to the unique brush patterns in your painting constitutes a creative contribution to your work. Why is a complex digital model which does the same any different?

Perhaps it is copyright as a whole that is wrong and is nothing to do with AI. This is what we get for creating imaginary property as a means to finance speculative creative endeavours in a capitalist system. So, yeah. Fun times there - once again technology challenges another economic status quo.

Multiple independently created compilers can directly translate source code to unoptimized machine code that works in a completely straightforward fashion based on the definition of the language. There’s a great deal of complexity involved in creating more optimized output, but the goal is to have functionally equivalent programs.

There’s no way to map DALLE prompts into any kind of obvious picture from the input. Even DALLE itself can produce a wide range of outputs from a single input.

There is, the input is the description of the image so produced plus the hidden elements and parameters (randomness, etc) that users often don't see - with these there is a deterministic input to output relationship. The fitness of the model is in how closely the output matches what we expect to see from them given the inputs we give. That's the point of them. Models are compilers. The distinction is really only in the complexity and ambiguity of the language specifications they implement - not in any fundamental aspect of their function. There isn't a single person alive who understands how a non-trivial compiler works in its entirety, just as nobody really knows how LLMs work yet. That's not the point.

That’s not “independently created” you’re suggesting reimplementing the output of a process not from first principles but from the output of the process. I can make a compiler in a programming language without it being a derivative work of any other compiler.

Further, people have programmed in languages before any compilers where created which worked after the compilers where created.

The CPU is a compiler for programs written in the machine instruction set architecture the CPU claims to implement which happens to output real world effects just as a compiler outputs program code. So, no, you can't.

No all CPU’s aren’t a compiler. Words have meanings and you used them incorrectly.

Early CPU’s didn’t compile anything they directly executed the instruction pipeline.

Words have meanings, and the instruction pipeline consists of electrical signals - and those early CPUs were almost all microcoded or had multiphase clocks or some other implementation abstraction which they did not expose to their architectural state... so yes, they were in a very real sense compilers.

Again “Almost” means not every. So no saying all CPU’s are compilers is clearly false from the words you just wrote.

Also, the number of CPU’s manufactured heavily favored very simple designs.

Simply because I didn't state "for all and every" doesn't invalidate my point, nor does it support yours as true - further, "heavily favored" suffers from the same problem. The point is, there's a system which takes as input formatted in a specification (a program) and some transformed output (a set of actions to be taken or another program input for another compiler). So, there you go. If a hot dog on a bun could be considered a sandwich, then a CPU could be considered to be a compiler. shrug disagree all you like.

If you say X is Y, but it’s not true for all X then the statement is false. Ie: “All integers are even.” is false.

As to your point that’s not what CPU’s do though, they have both a set of instructions and a set of IO with the outside world. A compiler always results in the same output from a given set of instructions, but with CPU’s you can run the same code and get wildly different output due to that IO.

The only way you can call a CPU a compiler is as a subset of its capabilities. If they they have internal microcodes where a given instruction gets translated into a different internal representation, but that’s not the end it also executes those microcodes.

Reply on news.ycombinator.com