clipka wrote:
> The bad companies will assimilate your free software project until, with their
> market power, they have "dried out" your project,

Name two.

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message

"Darren New" <dne### [at] sanrrcom> wrote in message
news:4980c287$1@news.povray.org...
> somebody wrote:
> > "Darren New" <dne### [at] sanrrcom> wrote in message
> > news:4980a265$1@news.povray.org...
> >> Jim Henderson wrote:

> >>>>   This makes GPL incompatible with all other licenses. This is rather
> >>>> restricting.

> >>> But protective of the rights of the original author, which is the
> >>> underlying goal.

> >> Which original author? The one giving away the code with more
> > restrictions,
> >> or the one giving away the code with fewer restrictions?

> > Rights of the author who released his code under GPL of course. Only in
the
> > bizzaro world might it make sense to assume GPL would offer protection
to
> > authors who don't (!?) use it.

> So you're agreeing. The GPL protects the freedoms of the author using the
> GPL

So far, I do agree.

> at the expense of the freedoms of the author using the MIT license.

This part is absolute nonsense. It's the MIT license that protects the right
of the author that is using the MIT license. Just like it's GPL license
that's protecting the rights of the author using the GPL license.

GPL neither protects, nor restricts the rights of anyone using any other
license. It's absurd to claim something like that, so I don't understand "at
the expense" part.

> And  the MIT license restricts users less in what they can do with the
code.

Maybe so, but that's irrelevant. The author can pick any license that he
wants. If the author wishes least restrictions upon the users, he won't pick
MIT either but release his code to public domain.

Post a reply to this message

"Darren New" <dne### [at] sanrrcom> wrote in message
news:4980c417$1@news.povray.org...

> If I include libjpg without modifying it at all, I can no longer use the
MIT
> license on my code,

So what? It's not your god given right to be able to use MIT license.

It's your option, however, to not use libjpg, if you don't agree to the
license.

> even if my code is orders of magnitude larger and more
> valuable.

That's neither here nor there. People don't have a right to code that's less
valuable than theirs.

> This forces me, while building something large that I need to get
> paid for, to rewrite code that's already tested and works well and is
> bug-free and safe. Hence, GPL code leads to bugs in non-GPL code.

That's some convoluted thinking. Libjpg is an option. You can take it or
leave it. Its existance doesn't force anything on you.

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
>   Could the reason why I argue against the GPL is that fanboys advocating
> it as something it's not ("you can use it in *any way* you want") are
> irritating?

You *can use* GPLed software in any way you want, including packaging together
with your closed software.  The GPL clauses only take effect in the case of
modification *and* release of modified GPLed software, not use.  Usage of GPLed
software is irrestrict to anyone to do as they see fit, including sell it
without further notice to the original developers.

What's irritating in this fact?

Post a reply to this message

somebody wrote:
> GPL neither protects, nor restricts the rights of anyone using any other
> license.

It does so by preventing you from using a different license. The GPL 
prevents you from linking code with a different license to GPLed code. The 
MIT license doesn't.

If you can't see that, then I'm not sure what the problem is.

> Maybe so, but that's irrelevant. The author can pick any license that he
> wants. 

Unless he's authoring a plug-in for GCC.

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message

nemesis wrote:
> Warp <war### [at] tagpovrayorg> wrote:
>>   Could the reason why I argue against the GPL is that fanboys advocating
>> it as something it's not ("you can use it in *any way* you want") are
>> irritating?
> 
> You *can use* GPLed software in any way you want, including packaging together
> with your closed software.  The GPL clauses only take effect in the case of
> modification *and* release of modified GPLed software, not use.

That's exactly what the /. article was talking about, tho. The intention is 
apparently to make it impossible to write a closed-source piece of software 
that interoperates with GCC without modifying GCC.  I.e., they're trying to 
prevent the author of plug-ins from distributing closed-source plug-ins that 
work with an unmodified gcc, in order to force the GPL onto those plug-ins.

See the subject line? Remember where we started?

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message

"clipka" <nomail@nomail> wrote:
> Darren New <dne### [at] sanrrcom> wrote:
> > If I include libjpg without modifying it at all, I can no longer use the MIT
> > license on my code, even if my code is orders of magnitude larger and more
> > valuable. This forces me, while building something large that I need to get
> > paid for, to rewrite code that's already tested and works well and is
> > bug-free and safe. Hence, GPL code leads to bugs in non-GPL code.
>
> Ooooh - you're one of the bad guys who try to steal free software, like libjpg!
> Don't you know that this piece of free software is only free as in "freedom of
> speach", and not as in "free for the taking"? Noooo, you gotta pay a price for
> that free library you intend to use!
>
> How much?
>
> Ooooh, nothing of particular value... just give us all rights to your complete
> application, including all other libraries it might be using - including the
> right to use it to acquire other software the same way as well - that'll be
> enough to settle the bill...

You're wrong.  GPL is a copyright-based license -- it absolutely depends on
copyright law to enforce its terms.  And you are the copyright owner to your
software.  You may dual license as well and this was the business model of
MySQL, at least until being acquired by Sun.

Post a reply to this message

somebody wrote:
> "Darren New" <dne### [at] sanrrcom> wrote in message
> news:4980c417$1@news.povray.org...
> 
>> If I include libjpg without modifying it at all, I can no longer use the
> MIT
>> license on my code,
> 
> So what? 

So you said "The GPL only affects those who modify the code." This is 
factually wrong, as evidenced by my example.

So that's the freedom that the GPL takes away from the user of the MIT 
license.  Since you asked.

And if I wanted to take some code licensed with the GPL and some code 
licensed with something more restrictive and combine the two, I couldn't.



> It's not your god given right to be able to use MIT license.

I'm not sure where I said it was.

I said the GPL restricts one person's freedom in return for another's, while 
some other licenses don't. You act like this isn't true, so I'm trying to 
explain it. Now that I realize that you understand this is true and just 
don't want to phrase it that way because then it wouldn't sound "free!" then 
I'll stop discussing it.

> That's some convoluted thinking. Libjpg is an option. You can take it or
> leave it. Its existance doesn't force anything on you.

But the license does.

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message

"clipka" <nomail@nomail> wrote:
> nemesis <nam### [at] gmailcom> wrote:
> > Oh, come on!  If you stopped whinning about sucky and evil GPL software
> > and pulled yourself together to write down replacement code for said
> > libs, you'd have by now a pretty large collection of good non-GPL
> > software under your belt.  After all, they are pretty trivial and simple
> > against your magnum opus.
>
> Isn't that just the same point the FSF is claiming about commercial software,
> just with a different "sign bit"?
>
> The bad companies will assimilate your free software project until, with their
> market power, they have "dried out" your project, so it only lives on as part
> of their closed, commercial code - and other similar free projects likewise, so
> the only alternatives left out there will be commercial products.
>
> What's the difference here to a bad FSF that will assimilate *my* free software
> project until, with *their* social power, they have "dried out" *my* project,
> so it only lives on under *their* GPL'ed, not-for-commercial license - and
> other similar free projects likewise, so the only alternatives left out there
> will be GPL'ed products...?
>
> I see people kind of measuring the one by the inches and the other by the
> centimeters here, while basically it's the same: Influential organizations
> trying to force their will on as much software as possible.

I see your point.  But I'd like to point out that your scenario of a GPL-only
environment is as ludicrous as a closed-source-only or BSD-only.  Closed
software will not die, despite highly successful free software projects and any
FSF advances.  There are projects which simply make no sense as shared
open-source projects.

That said, if you don't like GPL and its restrictions, it's just a matter of
choosing another source of well-maintained, bug-free software under a more
leech-friendly license.  Or create one your own!  I'm sure there are plenty of
anti-FSF developers out there ready to help you in your endeauvour.  and
benefit from it too... ;)

Post a reply to this message

Darren New <dne### [at] sanrrcom> wrote:
> So you said "The GPL only affects those who modify the code." This is
> factually wrong, as evidenced by my example.

Now I see your point.  However, a modification is considered here not simply the
act of taking the original code and messing with it.  A work derived from an
unmodified source is also a modification, "using" it to integrate its features
as base for a larger work.  That, I guess, is the crux of the matter with gcc
plugins.

It's a matter of perspective, of course.  They could very well allow for non-GPL
closed-source software to be plugins for gcc, but chose not to.  It's their
software and their terms.  The GPL doesn't require it and the GPL seems to be
living still in the older world of static linkage, but is slowly adapting to
new forms of composing software...

Of course, anyone courageous enough to fork gcc should stand right.  But I guess
most of these anti-FSF folks are more busy paying Microsoft for Visual Studio
and relegate gcc to geeky hobby.

Post a reply to this message