|
|
Subscribe / Log in / New account

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Mar 31, 2016 15:35 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
In reply to: Rust's Redox OS could show Linux a few new tricks (InfoWorld) by aggelos
Parent article: Rust's Redox OS could show Linux a few new tricks (InfoWorld)

> AFAICT, there's two arguments being made here, one implicit and one explicit. The implicit one is that libreadline is trivial and that it would be unfair for the authors of the proprietary code, which is decidedly nontrivial (a fact which I guess is intended to be reinforced by the presence of patents?), to "lose" "everything".
Libreadline is not exactly trivial but neither is it very complicated. It's not _fair_ that it should infect the whole code base.

Note, that it's entirely within the libreadline's authors right to impose such restrictions. I'm just saying that they are not even close to fair and the rational choice for libreadline users is to walk away.

If you add GPLv3 to the mix then it becomes not only unfair, but also political and deceptive.

> Would one expect sympathy if they somehow incorporated a competitor's proprietary code in their own proprietary project?
This is again a wrong analogy. The correct analogy would be a commercial library that prohibits its users from competing with library author's products.

> Having cleared the copyright considerations, we're left with nomenclature. IIUC, your argument, phrased in a non-propagandory fashion, is that 'hereditary' should apply to the weakest form of copyleft only (i.e. MPL or LGPLv2 with a static linking exception)
Correct. These licenses do not propagate outside of their "genetic line".

> whereas strong copyleft should be deemed 'viral'. IMHO, the 'viral' part has been thoroughly taken down
Incorrect. GPL _is_ viral. You might not like the connotations of it, but it IS viral.

And OF COURSE it's political. Everything is, even including the GPL itself. Should I quote the section 0 of it?


to post comments

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Mar 31, 2016 22:16 UTC (Thu) by raven667 (subscriber, #5198) [Link]

> It's not _fair_ that it should infect the whole code base.

As you point out, you have no rights to use the code whatsoever except for what the author grants to you, the fact that you think it unfair that the author doesn't allow you to help yourself to any code you find in any way you want is a fundamental disagreement that probably can't be resolved by furthering the discussion.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Mar 31, 2016 22:56 UTC (Thu) by anselm (subscriber, #2796) [Link] (6 responses)

GPL _is_ viral. You might not like the connotations of it, but it IS viral.

Real-life viruses don't require premeditated positive action on the part of their hosts in order to become active. While it is perfectly possible for you to catch a cold simply by being in the wrong place at the wrong time, your code can't be “infected” with the GPL unless you deliberately add GPL'ed stuff to it and then deliberately decide to distribute the result, which is a huge difference. Even then the GPL only applies to the combination of your work with the GPL'ed stuff – your stuff on its own can be licensed differently as long as the terms of its license don't restrict the rights that recipients of the combined result enjoy through the GPL. That is not how actual viruses work.

Calling the GPL “viral” is essentially propaganda.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 0:33 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (5 responses)

> Real-life viruses don't require premeditated positive action on the part of their hosts in order to become active.
Yes, and?

> Even then the GPL only applies to the combination of your work with the GPL'ed stuff – your stuff on its own can be _licensed_ _differently_ as long as the terms of its license don't restrict the rights that recipients of the combined result enjoy through the GPL.
No, it can't be in any meaningful way. GPL requires redistribution under GPL. Full stop.

It's just that some other open source licenses can be transparently and automatically upgraded to GPL.

> Calling the GPL “viral” is essentially propaganda.
So is "free software" which isn't actually free in any sense.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 10:36 UTC (Fri) by anselm (subscriber, #2796) [Link] (3 responses)

No, it can't be in any meaningful way. GPL requires redistribution under GPL. Full stop.

Non-GPL doesn't require redistribution under GPL simply because it might conceivably be brought together with GPL.

Suppose I write a program with a command-line interface and license the source code under the MIT licence. Both the source code and any resulting binaries can therefore be distributed under the terms of the MIT licence. If I add the build-system machinery required to optionally let people, if they so desire, link my program with a copy of GNU Readline (which is distributed under the GPL) that they supply themselves, that means a binary resulting from that operation must be distributed under the GPL if and only if these people deliberately decide to distribute it at all. That, however, in no way prevents me – or anyone else – from distributing the original source (or binaries that don't include GNU Readline) under the MIT licence. Even people who receive source for both my program and GNU Readline under the GPL applying to the combination binary would be free to distribute the source for my program, or binaries of my program that aren't linked to GNU Readline, under its original MIT licence. Hence the GPL on GNU Readline can't “infect” my original program against my wishes or the wishes of any recipient.

Of course if somebody intentionally decides to base a program on GPL'ed code where the GPL code isn't optional, that means the program can only be distributed in accordance with the GPL. But that is no different in principle from basing a program on code under some proprietary licence where the proprietary licence makes stipulations as to if and how the resulting program can be distributed. That's not “being viral”, it's just how copyright works. Generally if software authors don't like the way stuff they wish to use is licenced (GPL or otherwise), they're free to find alternatives with licences that are more acceptable to them. People who are “infected” with a “virus” usually have no such choice.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 10:51 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (2 responses)

> Suppose I write a program with a command-line interface and license the source code under the MIT licence. Both the source code and any resulting binaries can therefore be distributed under the terms of the MIT licence.
AND THAT'S WHAT I CALL FREAKINGLY DECEPTIVE. Please, stop doing this. It's about as honest as Trump's statements that he's the greatest supported of women's rights.

"Yes, sure. GPL totally doesn't require you to distribute code under GPL. You are also free to put it into the public domain or use MIT/BSD! Oh, and if you don't want to do THAT you're also free to settle for up to $150k per violation with each copyright holder. Have fun."

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 11:13 UTC (Fri) by anselm (subscriber, #2796) [Link]

It's about as honest as Trump's statements that he's the greatest supported of women's rights.

If you have anything to add except ad-hominem, let's hear it.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 18:51 UTC (Fri) by flussence (guest, #85566) [Link]

>"Yes, sure. GPL totally doesn't require you to distribute code under GPL. You are also free to put it into the public domain or use MIT/BSD! Oh, and if you don't want to do THAT you're also free to settle for up to $150k per violation with each copyright holder. Have fun."

Or more tersely: “If you want to screw over your users, foot the bill for development yourself.”

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 15:04 UTC (Fri) by aggelos (subscriber, #41752) [Link]

Real-life viruses don't require premeditated positive action on the part of their hosts in order to become active.
Yes, and?

And the 'virus' analogy is conclusively nonsense. Why keep pretending this is not the case? Honestly, your tireless repetition of the same narrative, without addressing the gross logical fallacies pointed out in it, feels like an attempt to shout people down. Even keeping up with all the implicit arguments and half-formed points is taxing. Could you at least put some effort into expressing yourself in a way that enables, rather than hindering, the discussion?

Calling the GPL “viral” is essentially propaganda.
So is "free software" which isn't actually free in any sense.

More like 4 senses. Freedom to run for any purpose, freedom to examine the source, freedom to distribute copies, freedom to collaborate on and distribute modified copies at least. This rhetoric remains as unconvincing as it is tiring :/ Is there any point in asking for intellectually respectful discussion any more?

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 9:11 UTC (Fri) by paulj (subscriber, #341) [Link] (4 responses)

If you don't like readline's licence, don't use it. If you find that it's "not fair" that you can't use readline on your own terms, well then I could equally think it's "not fair" that you're allowed to distribute your software as closed-source. In short, stop whinging that other people have the same rights to their code as you do over your own.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 9:34 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

Sure. And it would be nice if GPL fans stopped calling BSD/Apache-licensed projects "unfree" or "closeable source".

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 10:33 UTC (Fri) by paulj (subscriber, #341) [Link] (2 responses)

"free" has a specific meaning in the realm of Free Software licensing. Deliberately chosen to play on other meanings no doubt, but within that context "free" and the mirror "unfree" are correct descriptions of BSD/Apache.

"closeable source" on the other hand is just a generally descriptive term. BSD/Apache licence are explicitly designed to allow further mods to be kept closed!

I'm always amused by the more dogmatic BSD/Apache proponents who try to cast the GPL's attempt to keep code under that licence open as some restrictive of freedom, but who will get huffy if take their BSD/Apache code and - exactly as the licence allows and their espoused view of "freedom" seems to be in favour of - close it off.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 11:04 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

> "free" has a specific meaning in the realm of Free Software licensing. Deliberately chosen to play on other meanings no doubt, but within that context "free" and the mirror "unfree" are correct descriptions of BSD/Apache.
Then so is 'viral' for GPL. Why do you object to it? It has an entirely specific and accepted meaning in the realm of Free Software Licensing.

See: https://en.wikipedia.org/wiki/GNU_General_Public_License for references.

> I'm always amused by the more dogmatic BSD/Apache proponents who try to cast the GPL's attempt to keep code under that licence open as some restrictive of freedom
Yes, it is a clear limitation of freedom. FSF tries to justify it by their political goals, but it's still a restriction.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 11:28 UTC (Fri) by paulj (subscriber, #341) [Link]

The issue with "viral" is that it is just incorrect.

"free", I can totally agree that some might value open-preserving freedom more, while some might prefer closed-preserving freedom. There's an inherent trade-off there between the freedom for recipients to do whatever they want with the code, and the freedom of the code itself. You can not preserve both the freedom of the code and the freedom of recipients to do what they want. That's fine. In the context of FSF and copyleft, "free" means placing the freedom of the code above the freedom of people to close it. In the context of BSD/Apache, etc., it means preserving the freedom of recipients of the code, over the freedom of the code. Completely fine, they both make sense, they both have their place.

"viral" as an analogy to describe the GPL is not very good. All analogies fail at some point, but a good analogy at least holds for a while. However, GPL as a "virus" falls apart almost immediately. One does not have a choice, typically, in whether a virus will try infect you. Incorporating GPL code is however a choice.

Rust's Redox OS could show Linux a few new tricks (InfoWorld)

Posted Apr 1, 2016 14:55 UTC (Fri) by aggelos (subscriber, #41752) [Link]

AFAICT, there's two arguments being made here, one implicit and one explicit. The implicit one is that libreadline is trivial and that it would be unfair for the authors of the proprietary code, which is decidedly nontrivial (a fact which I guess is intended to be reinforced by the presence of patents?), to "lose" "everything".
Libreadline is not exactly trivial but neither is it very complicated. It's not _fair_ that it should infect the whole code base.

(Your comments persist on simply repeating terms that have been pointed out as knowingly (and grossly) misrepresentative ('infect'). To me, this seems like a propaganda campaign and definitely not an attempt at having an intellectually honest discussion.)

AIUI, the 'not fair' comment quoted above concerns the concept of 'derivative' in copyright law. IIUC, you think that it should be 'fair use' to call out to or embed a library and should not be subject to copyright limitations.

(meta: If you think the above is a misrepresentation of your thesis, please consider that it's hard to make out an argument among slogans that are clearly /not/ concerned with making a logical argument, rather with repeating a narrative. This is tiring work. I suspect that's not lost on you, but pointing it out all the same. Personally, I'm thinking that if LWN had some cap on the number or rate of comments per article by any single commenter, that might help with having a more concise discussion and make it easier for more people to be heard. Well, for well-intentioned people at least.)

If this is your point, then is not your frustration misdirected? Of course people who (a) do not want to help companies/individuals produce proprietary software and (b) want to incentivize people to knowingly participate in the production of free software will prevent appropriation of their code to the extent allowed by law.

Not that one can easily sympathize with your PoV -- AFAIUI, your argument is mostly concerned with enabling people to produce proprietary software. Which, it seems to me, is easy enough already (not to go into the larger discussion on whether free work for vendors of proprietary software is 'fair' or indeed whether further skewing the legal framework in favor of the production of proprietary software is socially useful). I mean, it's not like the set of laws concerning copyright and, especially, patents WRT software has been lobbied into existence by software freedom activists. Some might even say the current system started out and has largely evolved to cater to the needs and wants of proprietary software production (though, of course, different classes of proprietary software vendors have different requirements).

Note, that it's entirely within the libreadline's authors right to impose such restrictions. I'm just saying that they are not even close to fair and the rational choice for libreadline users is to walk away.

If you add GPLv3 to the mix then it becomes not only unfair, but also political and deceptive.

'political' isn't a slur. Everything we do has political connotations. When 'political' is used pejoratively, that seems like a way of telling people that they should not be thinking about politics, which seems hypocritical given the, I'm sure you'll agree, very much political narrative your comments have been reproducing. Also, given what we've read so far ('cancer', 'viral', 'infect', 'propagates'), I take issue with your calling anything deceptive. However, if you have an argument to that effect re: the GPLv3, please share it in a clear manner so that we can all consider its merits.

Your wording "libreadline users" seems ambiguous in this context

/Users/ of software using libreadline are probably happily reaping the benefits of using software that they can read the source of and, importantly, collaborate on, receive and distribute modified versions of.

/Developers/ who want to integrate readline in their product seem to be well aware what the licensing conditions are. People who want to develop proprietary software know that this code is not for them. People who want to develop free software may use this code, but they cannot permissively relicense or they would enable others to create proprietary derivatives. If they have reasons to require that their derivative be permissively licensed, they can consider their options and decide appropriately. I honestly fail to see where the (I hope you agree that's accurate) intense hatred of the GPL in your posts here stems from, other than the fact that it may disqualify some code from inclusion in proprietary programs.

Oh, and if you're going to talk about 'community splitting' again, we've already had that discussion here.

Would one expect sympathy if they somehow incorporated a competitor's proprietary code in their own proprietary project?
This is again a wrong analogy. The correct analogy would be a commercial library that prohibits its users from competing with library author's products.

That took quite a few re-reads to (maybe) figure out what you're talking about. IIUC, you're conflating code and people and making the argument that _code_ is a user of that library and hence the analogy should be with _people_ who are bound by an overreaching EULA? Again, IIUC (and your phrasing is really not helping), this seems quite confused. (a) As has been pointed out repeatedly, code does not have agency, its authors do (b) AFAIK, an EULA is /not/ a copyright license, but a contract. If there's an argument to be made here, kindly unpack it cause I, at least, cannot make sense of the above, and I tried to.

Having cleared the copyright considerations, we're left with nomenclature. IIUC, your argument, phrased in a non-propagandory fashion, is that 'hereditary' should apply to the weakest form of copyleft only (i.e. MPL or LGPLv2 with a static linking exception)
Correct. These licenses do not propagate outside of their "genetic line".
whereas strong copyleft should be deemed 'viral'. IMHO, the 'viral' part has been thoroughly taken down
Incorrect. GPL _is_ viral. You might not like the connotations of it, but it IS viral.

Umm, no-one can argue with 'incorrect' :-) Whatever arguments you've presented though...

And OF COURSE it's political. Everything is, even including the GPL itself. Should I quote the section 0 of it?

I think you misunderstood there. As explained above, 'political' is not a slur. However:

The word 'viral', when it comes to agency is so wrong that it seems clear to me that it's use is motivated by political views rather than any desire for accuracy.

i.e. your comments lead me to question your willingness to conduct a discussion (which might result in disagreement, sure) instead of engaging in posturing and staying on message re: cancer, viral, infectiousness and so on.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds