[em-bee]

that is not certain. if you read code and then reimplement it using the original code as reference, the claim has been made that this falls under the copyright of the original because the new code is derived from the old code. unfortunately this particular situation has not yet been tested in court. but clean room implementations are done specifically to avoid the risk reading the original code poses. if this was clear cut then clean room development would not be needed.

this is similar to creating an extension to some program, because the extension could not be written without the original even if the interface the extension is using is a public API. the claim has been made that the copyright of the original program applies. i think the linux kernel is an example here.

see also these questions on stackexchange:

https://softwareengineering.stackexchange.com/questions/2087...

https://softwareengineering.stackexchange.com/questions/8675...

[ranger_danger]

What if one reverse engineered the original logic, for example translating the assembly code into a higher level language. They didn't use or look at the original code. Does that still count as "clean room"? What's the legal difference between that and deriving the logic just from observing how the running program acts?

[em-bee]

there is no legal precedence that clarifies what clean room development is. clean room development is a precaution to stay away as far as possible from the original code in order to reduce the risk of infringement. clearly, not looking at the assembly code is better than looking at it.

[bigbadfeline]

> this is similar to creating an extension to some program

There's no such thing as "an extension to some program". A derivative work is a work that contains the original. Using the privileges provided by copyright law, the creator may impose licensing restrictions on how the original work is used - but that's contract law, not copyright.

For example the GPL and the AGPL define different sets of use restrictions, none of that matters in this case because the original work is not being reproduced or used per se.

As I already said in my other, down-voted comment - copyright is only about verbatim, or near verbatim copies, in whole or in part - it's the spirit that both judgment and the letter of the law are supposed to follow. Copying of functionality is not subject to copyright.

For example, one can use the same topic for a work of poetry for a similar aesthetic effect and that doesn't infringe other poems.

The GPL used a hack to stretch copyright law into a near opposite but stretching it further goes into absurd territory, achieving the opposite of what the GPL claims to protect.

[em-bee]

a kernel driver is an extension to the kernel. yet, even with a clearly defined API it is a derived work of the kernel.

one can use the same topic for a work of poetry for a similar aesthetic effect and that doesn't infringe other poems

because the new poem does not depend on the original.

the kernel driver is useless without the kernel

[bigbadfeline]

> a kernel driver is an extension to the kernel. yet, even with a clearly defined API it is a derived work of the kernel.

Maybe, in some alternative universe, that could be correct but it isn't anywhere on Earth.

You can write a BSD-licensed driver as a Linux module and distribute it separately all you want - copyright law is OK with that.

The moment you insert the module into the kernel the whole thing, kernel + driver becomes a derivative work and you're forbidden from using it by the GPL - the license, not copyright... Copyright only gives the creators of the kernel the privileged power to impose that contractual restriction.

Long time ago, some BSD guys were trying to convince me that the GPL was primarily a weapon against BSD and other less restrictive licenses but I didn't believe it back then... boy, was I wrong.

You showed me how the GPL can be used for threats against the free modification of software by arguing for the addition of new, absurd powers to copyright - the opposite of what the GPL proponents are promoting it for. It's indeed a license that must be avoided at all cost.

[em-bee]

not in an alternate universe, but it's a claim made by some free software people. i don't have time to search for a quote right now.

yes, it is disputed, and the claim has not been tested in court. but it is an argument being made.

the GPL was primarily a weapon against BSD.

It's indeed a license that must be avoided at all cost.

well, it depend on whose side you support. i am on the side of protecting the rights of the user to modify their software. BSD licenses don't do that. they give me the right, but they don't protect it.

more importantly, i am also on the side of the developer to protect their ability to make a living. for that the BSD license is completely useless. GPL is better, AGPL even more, but even those are not restrictive enough to prevent unfair competition by large corporations.

i am not interested in allowing those companies to benefit from my work if they are not required to pass that forward.

[bigbadfeline]

> but it's a claim made by some free software people.

In other words, you don't know what you're talking about... Everything I write is verifiable, have you heard of AI chat bots? Why are you going around asking old ladies for the latest gossip?

> yes, it is disputed, and the claim has not been tested in court.

Why don't you test in court? Do it, let's see what happens. Why did Linus wave middle fingers like a confused clown when Nvidia's lawyers stuffed the GPL2 with their driver? There was no lawsuit, only buffoonery in place of the promised "protection".

> but it is an argument being made.

There are millions of "arguments being made", 99.9% of them are BS, if you can't defend your arguments with facts, logic and court decisions don't waste e-space by regurgitating useless gossip, especially on HN.

> BSD licenses don't do that. they give me the right, but they don't protect it.

So, that's your reason to go on a crusade against the rights provided by BSD licenses.

Oh, that's sneaky - "Let's protect people from a license that gives them more rights than ours"

Your "protection" amounts to shilling for an absurdly extended interpretation of copyright powers while it's being sold as a defense against these very powers - this kind of diabolical nonsense is the opposite of protection.

[em-bee]

you may want to read the discussion here: https://lwn.net/Articles/998382/ "Is the GPL actually viral across dynamic linking?"

to quote one commenter there:

there's something socially wrong with taking someone's gift and ignoring the terms under which it was given. If you want a system where you can load any modules, use a BSD kernel. [...] If the creators of a GPL kernel label some items as an external API for anyone's use, and other items as GPL hooks for functionally internal code loaded externally, respect that.

me talking about "protection" is a call for solutions. if the interpretation of the GPL here is absurd, then the problem is not that it is wrong, but that the GPL does not provide enough protection. if you don' want that protection, fine, that's your choice. i do want that protection, and i am looking for solutions. if you are not interested in solving that problem then we don't need to continue this discussion.

[bigbadfeline]

in response to - https://news.ycombinator.com/item?id=47568753

> you may want to read the discussion "Is the GPL actually viral across dynamic linking?"

What does that have to do with the price of tea in China? We are talking about an independent implementation of a BSD driver for Ext4-strucutred storage but you keep bringing up unrelated random pieces of chatter from around the web.

> but that the GPL does not provide enough protection.

But you don't understand the difference between copyright and contract. The GPL, or any other license based on copyright, cannot prevent the creation of the driver in question because it doesn't involve any copying of the kind protected by copyright law.

> if you are not interested in solving that problem then we don't need to continue this discussion.

Except, that's not the problem we are discussing.

Indeed, there's no point in continuing this discussion, you don't understand the basics, cannot follow the line of reasoning and keep getting lost in hallucinations.