News for hackers. Stuff that matters.
Re:Why I am pro-GPL by epistasis on Tuesday July 21, 2015 @01:28PM (#9924009)
And that's a great thing to care about, and a great reason to create a license. The secondary question is: which license is best at perpetuating user freedom? This is a separate question than that of whether users should have freedom to mess with code. IMHO, the GPL is not the best license for perpetuating the most user freedom. Many people disagree with me on this, but their disagreement usually comes down to "the GPL is best for user freedom because it was created for user freedom and RMS is talking about user freedom." I'm not yet convinced that MIT-like, BSD-like, and Apache-like are any worse at perpetuating user freedom, and may in fact be far better at perpetuating user freedom due to their greater acceptance.
Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @01:42PM (#9924172)
> I'm not yet convinced that MIT-like, BSD-like, and Apache-like are any worse at perpetuating user freedom, and may in fact be far better at perpetuating user freedom due to their greater acceptance.

Well, the GPL mandates the right to use the application, and that a redistributor cannot restrict it (section 0, preambule and section 6, IIRC); that right is not guaranteed by MIT, BSD, MPL or Apache.

Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @01:55PM (#9924290)
>Well, the GPL mandates the right to use the application, and that a redistributor cannot restrict it (section 0, preambule and section 6, IIRC); that right is not guaranteed by MIT, BSD, MPL or Apache.

Yeah, and because of the additional restrictions of GPL, big companies are simply avoiding it or writing software to replace it.

See: CLANG/LLVM. GCC used to be the king of the compiler heap; now it's well on its way to becoming an historical footnote.

It's far better to convince people to help you by being trusting and generous than by coercion. The GPL uses coercion.

Yes, some companies use BSD/MIT software and lock it up, never to send improvements back upstream. But they ultimately are harming themselves, as they can't trivially update to new versions of the the software, because they're now maintaining a fork, and the longer their code diverges, the harder it will be to maintain. So they are motivated to send improvements upstream. And many (most?) big companies do.

When there's another game in town, people will play the one where they're more welcome. Open source software benefits by many eyes and many hands; the GPL (especially GPLv3) cuts off access to just about everyone in big companies, which means the size of the potential user base is a fraction of what it can be.

Linux is a notable exception, obviously. But with Linux there's a clear way to use it that doesn't risk your proprietary code. Most other software, not so much.

Re:Why I am pro-GPL by xirdstl on Tuesday July 21, 2015 @02:17PM (#9924480)
I'd go further and say it's not just big companies. I've worked for big companies and small, and they have all avoided GPL as much as possible.

It is worse, though, in larger companies. There is generally several layers more of bureaucracy to get through to be able to use GPL licensed software.

To be clear, I'm speaking of my role as a developer and using GPL software in developing proprietary software.

Re:Why I am pro-GPL by weland on Tuesday July 21, 2015 @02:50PM (#9924744)
I've worked for a small company and we had similar problems. It's not that you have to convince six layers of bureaucrats who have no idea what GPL is but they read in eWeek that it's scary -- it's simply that, when you're that small, long-winded consulting services from IP lawyers is not the kind of stuff you want to spend money on.
Re:Why I am pro-GPL by Nelson69 on Tuesday July 21, 2015 @02:52PM (#9924768)
> Yes, some companies use BSD/MIT software and lock it up, never to send improvements back upstream. But they ultimately are harming themselves, as they can't trivially update to new versions of the the software, because they're now maintaining a fork, and the longer their code diverges, the harder it will be to maintain. So they are motivated to send improvements upstream. And many (most?) big companies do.

Is there any evidence of this?

Re:Why I am pro-GPL by 0x09 on Tuesday July 21, 2015 @04:50PM (#9925710)
Sony has spoken about the problems associated with maintaining a private fork of Clang for the toolchain of the then-unreleased PS4.

See "Working with the LLVM community": http://llvm.org/devmtg/2013-11/slides/Robinson-PS4Toolchain....

Re:Why I am pro-GPL by dman on Tuesday July 21, 2015 @02:03PM (#9924354)
Could you provide some supporting arguments / evidence for this statement - "GCC used to be the king of the compiler heap; now it's well on its way to becoming an historical footnote." ?
Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @02:15PM (#9924451)
* As pointed out by another commenter, Apple switched away from GCC as the default to CLANG.

* Microsoft is supporting CLANG.

* Android switched from GCC default to CLANG default.

* The CLANG development community, combined with the LLVM development community, are both extremely robust.

* GCC used to have full time commercial developer contributors working for Google and Apple and other large companies; most such companies have migrated almost entirely to CLANG/LLVM support.

* Because of better management and the army of full time commercial developers contributing to it, CLANG is better in practically every conceivable way at this point than GCC. If GCC weren't GPL, CLANG would likely be (at most) a fork of GCC, and may have been merged back into trunk by now (this happened to GCC once before).

CLANG is also an excellent example of how a completely permissive license can be sufficient to encourage big companies to contribute their changes back to the commons. All of the GPL fearmongering would have you believe that CLANG couldn't exist, and yet it thrives.

And printer drivers are still almost all proprietary [1]. So GPL didn't even achieve the objective that inspired it.

GPL did prove that open source CAN work, and it jumpstarted the open source movement. But its time has past; enough people understand the benefits of contributing to open source that the coercion is no longer necessary, and in fact is harmful.

[1] Some printer drivers have been reverse-engineered for Linux, certainly. But modern printers frequently leave so much processing for the host that their drivers are nontrivial, and even when there exists "free" drivers for Linux, they pale in comparison feature-wise to the proprietary drivers. I'm sure there are exceptions.

Re:Why I am pro-GPL by timtadh on Tuesday July 21, 2015 @02:49PM (#9924735)
LLVM was not created as reaction against the licensing model of GCC. It was created as a research project exploring: "transparent, lifelong program analysis and transformation for arbitrary programs."[1] GCC and other compilers were not setup to do this. They needed to build an intermediate representation of a kind that was highly unusual for the time. That is where it originated, as pure research. Trying to build a better mouse trap. Not to become a GCC competitor. It did become one because it turned out they had some rather good ideas!

The GPL is not harmful and I encourage you to utilize it when appropriate for it protects you (the original author) and your target users far more than BSD or other similar licenses.

[1] http://llvm.org/pubs/2004-01-30-CGO-LLVM.html Read full paper not just the abstract to get the full picture.

Re:Why I am pro-GPL by bsder on Tuesday July 21, 2015 @04:15PM (#9925427)
> It was created as a research project exploring: "transparent, lifelong program analysis and transformation for arbitrary programs."[1] GCC and other compilers were not setup to do this.

gcc was in fact set up to explicitly not be able to do this.

The developers of gcc made understanding the intermediate forms as well as creating plugins as hard as possible specifically so that you couldn't get around the GPL.

clang a direct result of attempting to coerce people with real money with the GPL.

Re:Why I am pro-GPL by timtadh on Tuesday July 21, 2015 @05:15PM (#9925868)
> > It was created as a research project exploring: "transparent, lifelong program analysis and transformation for arbitrary programs."[1] GCC and other compilers were not setup to do this.

> gcc was in fact set up to explicitly not be able to do this.

GCC was originally very difficult to integrate with so that non-free programs could not be built on top of it. However, the creation of LLVM does not reduce to: "GCC was difficult to work with so we made this." There had been many attempts to make "Universal Compiler IRs". These attempts had not gone well. LLVM instead chose to do something at a unique level of abstraction that wasn't good for everything but was very good for its particular niche. Once again, read the paper, LLVM really wasn't created as a reaction against GCC.

Re:Why I am pro-GPL by Tyr42 on Tuesday July 21, 2015 @02:34PM (#9924613)
I feel like the GPL-ness of gcc was less material than the fact that it's developers were afraid of closed source frontends benefiting from their work, and obfuscating the front end so that it was hard to use without pulling in the rest of the codebase.

And the reason I switched was because Clang had better error messages.

Re:Why I am pro-GPL by GFK_of_xmaspast on Tuesday July 21, 2015 @02:57PM (#9924815)
c.f. Stallman squashing the exportation of ASTs from gcc for use in emacs earlier this year.
Re:Why I am pro-GPL by nickpsecurity on Tuesday July 21, 2015 @03:18PM (#9924979)
Like other commenters, I think GPL had little to do with switch to Clang/LLVM. I liked it for its better, versatile design with a community turning it into the program analysis/transformation baseline to beat them all (minus Semantic Design stuff maybe). However, I think your overall point is supported by the fact that many virtualization solutions in embedded space are marketing GPL isolation as a benefit worth buying them. They probably wouldn't be saying it unless they had lots of customers talking about that problem.
Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @08:03PM (#9926802)
Interesting point about the virtualization. MANY companies are scared of GPL, for certain.

Thinking about Clang, its better design didn't evolve in a vacuum. Clang was primarily developed by Apple [1] so that they would have (with LLVM) a full compiler toolchain that didn't include GPL code (and as others have mentioned, Clang is designed to integrate with editors for parsing, while GCC is explicitly designed to be HARD to integrate that way so that it can't be snuck into a proprietary project).

YOUR choice to change to Clang may not have been about licensing, but licensing and design choices in support of that license philosophy are what caused Clang to exist.

[1] https://en.wikipedia.org/wiki/Clang

Re:Why I am pro-GPL by wooger on Wednesday July 22, 2015 @07:41AM (#9928959)
This gives the worrying possibiltiy that Apple can benefit from an open source Clang and LLVM now, and in future can make thecomponents required to compile code to their platforms (mainly thinking iOS) proprietary.

They're already moving to encourage / require iOS devs to ship them LLVM IR code - the most logical reason for this is so that they can keep the last part of compilation entirely proprietary in future, taking further freedoms from users and developers.

They design and fab their own ARM chips already, so this is plausible.

Re:Why I am pro-GPL by nickpsecurity on Wednesday July 22, 2015 @12:57PM (#9930813)
Exactly. They did that sort of thing with Mac OS and iOS on Darwin. They're doing it with Clang. They always do it. It's how they make billions of dollars. Not sure why you worry whether a particular company might scheme: simply don't buy their stuff.

See how that works? And despite Google's BS, I have plenty of ways to keep Android devices largely under my control. On that side of the fence, people stopped worrying and started modding en masse. :)

Further, mobile security vendors such as OK Labs w/ OKL4 let us isolate that mess while programming directly on the kernel or a custom runtime (think MirageOS for mobile). So, we have plenty of options because we aligned with a company doing open-source mobile with little lock-in. Align with closed-source and lock-in loving companies then you get what you had coming. ;)

Re:Why I am pro-GPL by TD-Linux on Wednesday July 22, 2015 @10:24AM (#9929789)
They also of course did the opposite with Swift - created a proprietary front end.
Re:Why I am pro-GPL by nickpsecurity on Tuesday July 21, 2015 @11:36PM (#9927598)
My choice was about licensing and design but 90+% design given GCC was a pain to work with. Your link shows two paragraphs of text talking about design issues with one sentence on licensing. So, it seems Apple's justifications were more similar to my own than different.

The best part is that so many have jumped on the LLVM bandwagon. There's even a formal semantics to get formal verification work going. Mainstream coders, tool developers, and high assurance people all under the same roof contributing a bit to the same tool. Lots of potential there.

Re:Why I am pro-GPL by fegu on Tuesday July 21, 2015 @02:53PM (#9924770)
FreeBSD has switched from GCC to clang as well.
Re:Why I am pro-GPL by dman on Tuesday July 21, 2015 @02:54PM (#9924783)
Thanks for writing this up, you make some excellent points. Could you comment on why the BSD's (FreeBSD / OpenBSD / NetBSD) has so far not made inroads against Linux which happens to be GPL2 licensed?
Re:Why I am pro-GPL by microtherion on Tuesday July 21, 2015 @06:43PM (#9926401)
First of all, BSD, in the form of OS X and iOS, is more than holding its own.

On the desktop, I believe that BSD was (a) hamstrung by the AT&T / BSDI lawsuit at a critical time and (b) suffered from fragmentation brought about more by incompatible forceful personalities than by technical issues.

Re:Why I am pro-GPL by wooger on Wednesday July 22, 2015 @07:43AM (#9928971)
Please stop this bizarre insistence that OS X = BSD. Different kernel, radically different OS overall, not open sourced.

Still shares some userland, but this is irrelevant.

For a true picture, look at how well their open sourced Darwin OS project is doing in terms of update and support.

Apple gutted the FreeBSD core team back in the 90s, hiring them all away.

Re:Why I am pro-GPL by microtherion on Thursday July 23, 2015 @04:14PM (#9938205)
Different kernel

But fairly similar userland.

Still shares some userland, but this is irrelevant.

I would say that for most people, the API matters far more than the kernel implementing it.

not open sourced

http://www.opensource.apple.com has the kernel sources under "xnu". I don't think that substantially less is open sourced than e.g. for Android.

look at how well their open sourced Darwin OS project is doing in terms of update and support

The updates are fairly current (10.10.1 corresponds to the version of OS X shipped last fall), though there doesn't seem to be a very large community building on it.

Re:Why I am pro-GPL by cjbprime on Tuesday July 21, 2015 @11:13PM (#9927537)
> First of all, BSD, in the form of OS X and iOS, is more than holding its own.

Those are proprietary forms. I think we were talking about whether the decision to be BSD-licensed has been good for the health and contribution of the *BSD projects that OS X and iOS originated from. Then we can draw a conclusion (but hopefully after gathering more data) on whether releasing your codebase GPL or BSD is more likely to lead to long-term health for that open source codebase.

Re:Why I am pro-GPL by cwyers on Tuesday July 21, 2015 @02:58PM (#9924816)
But was GCC ever top of the heap, compared to stuff like Intel's compiler and Microsoft VC++?
Re:Why I am pro-GPL by dman on Tuesday July 21, 2015 @03:05PM (#9924865)
http://blog.pgaddict.com/posts/postgresql-performance-with-g...

https://www.phoronix.com/scan.php?page=article&item=clang-gc...

Show gcc and clang to be broadly competitive without a clear winner in terms of speed of execution.

Re:Why I am pro-GPL by jcranmer on Tuesday July 21, 2015 @02:21PM (#9924517)
A more accurate statement would be that gcc ceded an entire market to Clang. Clang made a big deal about static analysis and tooling for C++ programs, in effect bringing advances in software engineering and tooling made for Java/C# to C/C++. The hostility to making gcc's parsers be more usable by other applications (GCC plugins only very barely made it into the tree) makes Clang the de facto solution; given differences between ASTs, there's also a strong network effect--if you start using Clang, you'll find it hard to switch to gcc and vice versa.
Re:Why I am pro-GPL by dman on Tuesday July 21, 2015 @03:00PM (#9924833)
I dont know if licensing was the only reason why GCC missed out on this market. Using parts of the compiler as a library to aid tool building, refactoring and analysis is one of those great ideas that seems obvious in retrospect. To the credit of LLVM's early authors they had a larger vision of what a compiler ought to be than other compilers at the time. I dont recall gcc or any of the other commercial compilers having this expansionary vision of a compiler stack back in the 2000s. Once LLVM was able to move the goalposts on what users expect from a compiler stack, I can see that the license could have eased the decision for the likes of Google and Apple to come on board. It would be interesting if someone from Google / Apple / Microsoft commented on what the thought process was regarding moving to LLVM / Clang and if licensing played a role.
Re:Why I am pro-GPL by david-given on Tuesday July 21, 2015 @02:16PM (#9924469)
Evidence, not so much, but I've got anecdata, if that's any help:

I used to work for a company which produced a game-playing virtual machine. We had a toolchain that allowed building C and C++ programs for it. The toolchain was based on LLVM and gcc (because clang wasn't around at the time).

Integrating gcc into our toolchain was appallingly hard, solely due to GPL restrictions. The extra work in dividing everything into GPL and non-GPL parts, interfacing between the two, producing split packaging and distribution etc was basically half a full time job.

If the company had survived long enough for clang to have become stable --- which, sigh, it didn't --- we would have switched to it like a shot.

Re:Why I am pro-GPL by jcl on Wednesday July 22, 2015 @02:26AM (#9928016)
Clang is not a good example... It was adopted by Apple for its technical merits over gcc rather than its license. And, in fact, Apple tried to license clang/llvm under the GPL as a contribution to gcc but was rejected:

http://www.phoronix.com/scan.php?page=news_item&px=MTU4MzE

That clang is not GPL is more an accident of history than a preference of licenses:

https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00...

Re:Why I am pro-GPL by andmarios on Tuesday July 21, 2015 @02:51PM (#9924761)
Webkit is GPL. Android (Linux) kernel is GPL. CUPS is GPL. Busybox is GPL.

Companies may try to avoid GPL but only if they have another, viable choice.

Re:Why I am pro-GPL by xyzzyz on Tuesday July 21, 2015 @06:40PM (#9926388)
Nit: Webkit is not GPL. It's partially LGPL, and partially BSD.
Re:Why I am pro-GPL by microtherion on Tuesday July 21, 2015 @06:45PM (#9926411)
In the case of CUPS, Apple's choice appears to have been to buy a license exemption for themselves.
Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @02:16PM (#9924463)
> Yeah, and because of the additional restrictions of GPL, big companies are simply avoiding it or writing software to replace it.

Sure, and my point was to answer the parent about what freedom does the GPL grant to the users.

Your point is interesting, but is totally besides what I was saying, or the parent.

Re:Why I am pro-GPL by epistasis on Tuesday July 21, 2015 @02:36PM (#9924640)
No, his point was exactly why I don't believe that permissive licenses are any worse at perpetuating user freedom than coercive licenses like the GPL: when one feels coerced by a license, the option is to just not take it at all. Whereas with a permissive license, one is far more likely to take it initially, and then perhaps share alike afterwards.

Those who wouldn't share under a permissive license wouldn't accept the GPL to start with, so what additional user freedom can the GPL possibly create in the world that's not already there with permissive licenses?

Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @02:43PM (#9924680)
You are speaking of feelings, I speak about facts and what's actually written in the license: the GPL forbids restricting the freedom to use, even when redistributing; the other licenses don't. This is a clear user freedom that is guaranteed by the GPL.
Re:Why I am pro-GPL by SomeCallMeTim on Wednesday July 22, 2015 @02:26AM (#9928018)
>This is a clear user freedom that is guaranteed by the GPL.

Yes, and that freedom is being guaranteed to fewer and fewer end users of GPLed software because of those feelings you're dismissing.

Linux is probably the success story for GPL, and even in that case Google has bundled it with proprietary software (Android now outnumbers all other operating system installs, IIRC). Yes people can make their own distributions, but they're for the most part irrelevant to 99% of users of Android devices. Probably 99.99% if you include people who never install Google proprietary apps (the Play Store; Google Maps; etc.) on their devices.

The point of GPL wasn't to serve the 1%, but to expand software freedoms to everyone. To start a revolution in software, and to supplant closed source and restrictive licenses. Look around, though; most people are ignoring what freedoms they are offered and basking in proprietary software options.

Open source is beautiful when it works. But freedom to redistribute something without value is about as relevant as debating whether a tree falling alone in a forest makes a noise.

Re:Why I am pro-GPL by epistasis on Tuesday July 21, 2015 @03:38PM (#9925130)
Feelings are incredibly important around these things! Dismissing them as unimportant misses a huge part of humanity, and of freedom itself.
Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @02:38PM (#9924647)
> but is totally besides what I was saying, or the parent.

No, it's not.

GPL is only relevant if it can grant freedom to modify software that's relevant. Freedom to modify something you don't really want to use has no value.

Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @02:45PM (#9924693)
The parents speaks about USER freedom, not about developers or redistributors. You argue that freedom of developers is more important, and that's fine. But don't say that the GPL does not guarantee more user freedom.
Re:Why I am pro-GPL by cwyers on Tuesday July 21, 2015 @03:17PM (#9924970)
I think you're talking past each other. The GPL only guarantees user freedoms if you're a user of software licensed under the GPL. If you're using non-GPL software, then the GPL's protections don't matter. If GPL software isn't as good as non-GPL software (for many different, sometimes conflicting definitions of good), it will have fewer users and thus the GPL will provide freedoms to fewer users.
Re:Why I am pro-GPL by SomeCallMeTim on Wednesday July 22, 2015 @02:09AM (#9927973)
Thank you.
Re:Why I am pro-GPL by clacke2 on Wednesday July 22, 2015 @05:20PM (#9932365)
Non-coercion fails with LLVM:

"indeed there are multiple proprietary compilers and utilities built on top of LLVM—including Apple's Xcode and NVIDIA's CUDA compiler."

https://lwn.net/Articles/582697/

OpenStack is one of the biggest permissively-licensed free software projects out there:

""" Everyone I know who is deploying OpenStack has forked. Not publicly, but they have. No one can run the mainline code, it’s a disaster, and OpenStack politics of the “Big Tent” are going to make that problem a lot worse. Because everyone has their own fork, very little code is making it back upstream. """

http://gigofham.com/archives/47

Re:Why I am pro-GPL by Aldo_MX on Tuesday July 21, 2015 @01:50PM (#9924247)
>Well, the GPL mandates the right to use the application, and that a redistributor cannot restrict it (section 0, preambule and section 6, IIRC); that right is not guaranteed by MIT, BSD, MPL or Apache.

I've yet to see a person who hasn't been able to get the free version of Lua/zlib/libjpeg/libpng/etc. just because some of its rights were restricted by a commercial product (ex. a game).

I'm not saying that the GPL is a bad license, but I personally believe that people who defend it by saying it gives you "more freedom" than MIT/BSD/Apache-like licenses should do a reality check first. More freedom in legalese doesn't equal more freedom in practice.

Re:Why I am pro-GPL by pornel on Tuesday July 21, 2015 @03:22PM (#9925012)
There are two different situations where this matters:

1. When lua/zlib/libjpeg is compiled into a closed system (perhaps even with DRM), you can't modify that copy of the library. For example you don't have freedom to replace your iPhone's JPEG encoder with MozJPEG.

2. GPL code only helps projects that respect users' freedom, so only Free projects can benefit from it. OTOH do-whatever-you-want code helps both Free and closed projects alike. It allows user-hostile projects to take gratis code, add one (mis)feature, and with little effort compete with the open-source version (see: majority of Android market share belongs to derivatives with unremovable crapware and locked bootloaders).

It's hard to argue about overall effect in practice — it expands problem from legalese to politics. Maybe carriers would never let Android to take off if it was GPL-licensed, but OTOH a GPL3-licensed Android now would be great: it would still allow vendors to customize and extend it, but wouldn't force users to put up with unremovable crapware.

Re:Why I am pro-GPL by Aldo_MX on Tuesday July 21, 2015 @04:27PM (#9925534)
1. Actually you can, it's not pretty because it involves code injection, but you can.

But anyway, the question is "which kind of end user would want to switch a JPEG encoder and doesn't know about code injection"? Certainly not many.

Quoting a comment from above:

GPL is only relevant if it can grant freedom to modify software that's relevant. Freedom to modify something you don't really want to use has no value.

2. I hardly see the issue with the Android example, even if Android were GPL-ed, the carriers would include unremovable crapware, because the GPL license doesn't apply to external files.

Re:Why I am pro-GPL by pornel on Tuesday July 21, 2015 @05:56PM (#9926149)
1. I've meant "can" more as allowed by proprietary licenses and laws like DMCA (by which you can't), than in the hacker sense that you can break all DRM you want and declare copyright is bullshit anyway.

> the question is "which kind of end user would want to …

No, that's completely missing the point. It's like "We don't need freedom of speech, because most people have nothing interesting to say".

2. GPL3 has anti-tivoization clause, so if they modified Android to prevent removal of any program (closed or not) you would have right to reverse that change and get rid of the crapware.

Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @02:14PM (#9924450)
I'm sorry, but you are answering on the side to what I've said. It's about freedom to use, not to get/modify/redistribute.
Re:Why I am pro-GPL by Aldo_MX on Tuesday July 21, 2015 @02:31PM (#9924594)
What's the difference? If you want to use zlib in a project you are making, you proceed to get the free version of zlib first, you are not going to take the version of zlib from a commercial product.
Re:Why I am pro-GPL by jbk on Tuesday July 21, 2015 @02:36PM (#9924634)
You are speaking of developer freedom, not end-user freedom, which was parent's question. zlib is a library, not an end-user application.
Re:Why I am pro-GPL by thegeomaster on Tuesday July 21, 2015 @01:41PM (#9924154)
I understand your argument, but there's another side of that coin. An MIT licensed piece of software can be taken by a company, improved in-house and distributed as proprietary, thereby depleting the community of improvements to the work they have made freely available under good faith. GPL also demands that all distributions contain source code so the user has freedom of tinkering with and inspecting the piece of software as they see fit; the core philosophy, as I understand it, is that since software is to be run on users' computers, they have a right to see how it works, what it does, and change its behavior if there is a need for that. I'm not advocating for blindly using GPL wherever one gets a chance (even RMS and the FSF use the more permissive LGPL for some of their work, most notably GNU Readline), but there are some compelling reasons for releasing your code under GPL, which are of course dependent on your particular case (there seems to be no one-size-fits-all solution for open-source/free software licensing).
Re:Why I am pro-GPL by Karunamon on Tuesday July 21, 2015 @01:43PM (#9924176)
An MIT licensed piece of software can be taken by a company, improved in-house and distributed as proprietary, thereby depleting the community of improvements to the work they have made freely available under good faith.

However, this hypothetical ignores the reality that companies will often simply not touch GPL code rather than deal with compliance. It's not a choice between the MIT licensed code and the GPL licensed code, it's a choice between the MIT licensed code or anything else. Including reinventing that particular wheel in house.

(opinion follows)

In other words, the GPL reduces the amount of quality (software) in the world and ties developers' hands for the purposes of an ill-thought-out political goal. More annoyingly, it does so in the guise of user freedom, when in reality, the GPL does almost nothing for people who don't hack on code.

Re:Why I am pro-GPL by mordocai on Tuesday July 21, 2015 @01:51PM (#9924256)
See Linux as a counter-point to this argument.

If your software is good enough, has enough grass-roots support from developers, and has a good/large community around it then companies will bit the bullet and use it despite it being GPL.

Re:Why I am pro-GPL by baddox on Tuesday July 21, 2015 @02:21PM (#9924514)
An example of a GPL project that companies do touch is not a counterpoint to the argument that lots of companies refuse to touch lots of GPL code.
Re:Why I am pro-GPL by pessimizer on Tuesday July 21, 2015 @02:29PM (#9924572)
An example of a GPL project that most companies do touch is a counterpoint to the argument that the GPL prevents companies from using software.

That lots of companies refuse to touch GPL code is not an argument for the proposition that "the GPL reduces the amount of quality (software) in the world."

Re:Why I am pro-GPL by Aldo_MX on Tuesday July 21, 2015 @02:19PM (#9924492)
The kernel? Because I've yet to see a Linux distro that doesn't work better with non-GPL parts (ex. Proprietary Drivers).
Re:Why I am pro-GPL by mordocai on Tuesday July 21, 2015 @02:47PM (#9924724)
Only for hardware. Typically for wireless and video drivers. If you use an Intel video card and Intel wireless (the former of which you can only do if you don't care for intensive 3D apps) then you can get away with no OS level proprietary software.

Pretty easy to do if your only use of the machine is development work. Once you get into gaming you have to pile a ton of proprietary software (OS and otherwise) if you want to play anything recent.

Re:Why I am pro-GPL by minot on Tuesday July 21, 2015 @01:55PM (#9924292)
> In other words, the GPL reduces the amount of quality (software) in the world and ties developers' hands for the purposes of an ill-thought-out political goal.

I believe this is a plus point of GPLv3 (although more of a side-effect than a goal). I cheer for companies like Artifex which develops Ghostscript. It makes sense to me that if you're not willing to pay forward, you must pay back towards the cost of developing software.

But then, I've never had to make these hard choices so my naivety shows here.

Re:Why I am pro-GPL by rdtsc on Tuesday July 21, 2015 @01:51PM (#9924258)
> However, this hypothetical ignores the reality that companies will often simply not touch GPL code rather than deal with compliances

Some companies do they get a proprietary license from the authors in return for payment. I've seen companies pay for that. So answer doesn't necessarily have to be "we have to release all our code" it could also be the common business answer of -- pay and get a license.

Re:Why I am pro-GPL by vezzy-fnord on Tuesday July 21, 2015 @01:56PM (#9924302)
the GPL does almost nothing for people who don't hack on code

Yes, it does. Because of copyleft reciprocity, all users benefit from modified and enhanced copies to the software.

Re:Why I am pro-GPL by kstenerud on Tuesday July 21, 2015 @02:26PM (#9924559)
Except for the loss in innovation due to companies that will not touch GPL for fear of being forced to divulge the trade secrets in their code.

If a company could be sure that nothing in their code could jeopardize their competitive advantage, there'd be no problem with exposing it to the world. But the real world often doesn't work that way. And to make matters even worse, people often get it wrong when deciding what needs to be protected, and what doesn't.

Re:Why I am pro-GPL by Spivak on Tuesday July 21, 2015 @03:08PM (#9924902)
> Except for the loss in innovation due to companies that will not touch GPL for fear of being forced to divulge the trade secrets in their code.

That's exactly the point of the GPL. Look, we as human beings would be all better off without trade secrets, without closed source, and with the explicit permission to tinker, modify, and improve the products we use every day.

You as a user should want all of the rights afforded to you by the GPL. You should want to know how all of your devices work. You should want to be able to do what you please with them and not just what the company you bought it from wants you to do with it.

Yes, we get it, companies don't want to tell people their secrets, but that's not the fault of the GPL. It's the fault of every user like you who is apathetic toward proprietary software, who thinks it's okay to exploit and profit off of others ignorance while perpetuating a legal framework that mandates that ignorance.

Re:Why I am pro-GPL by pbreit on Tuesday July 21, 2015 @04:21PM (#9925478)
"we as human beings would be all better off without trade secrets, without closed source, and with the explicit permission to tinker, modify, and improve the products we use every day."

So, without Apple products? I don't think so. Far from it.

Re:Why I am pro-GPL by marrs on Tuesday July 21, 2015 @09:54PM (#9927261)
Are you joking? Apple products are the most locked down and functionally inept of them all. Remind me again how I can drag and drop music onto my iPod, or for that matter play an ogg or flac file on it, or switch to a different task on my Mac without its app and all of its windows taking over my entire desktop, or lock my screen without knowing some arcane keyboard shortcut, or find my home directory in the finder?

Not only is OS X by far the hardest to learn and use of any of the desktops, free or non-free, it is also the least customisable. I can't even buy software to make the window manager usable because Apple won't provide the API to make it possible.

Re:Why I am pro-GPL by zobzu on Tuesday July 21, 2015 @02:57PM (#9924811)
Since MIT-style licensed code gets close sourced I don't see how your logic works at all. Only few huge projects will share back, and generally only share back partially.

If companies are going to choose closed-source license over open sourcing their own code if not GPL or MIT or similar code is available, they weren't going to help open source code to being with.

Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @02:08PM (#9924401)
>depleting the community of improvements to the work they have made freely available under good faith

What is this insane logic?

If someone modifies my code and doesn't give it to me, it doesn't deplete me of anything. For that to be true I would have to lose something I already possessed.

You maybe meant "deprive," but at no time did I ever have a right to anything that they created. It seems you're asserting that because they used my code I suddenly should have a right to use their modifications. I think that logic is flawed.

I do believe I should have a right to use anything I've created [1]. And if someone feels they've made changes that would be generally useful, and submits code to add to the code I've released, then I would be thankful.

But I wouldn't feel that I had the right to something created by someone else just because I gave them a gift that didn't even cost me anything to give them (aside from possible opportunity costs).

That's not to say that GPLv2 isn't useful for dual-licensing situations (like Qt), so as to convince companies to pay for full commercial use. But the latter situation does NOT guarantee user freedom (people will only pay if they AREN'T willing to release code, after all), and the pro-GPL arguments on this article seem to focus on user freedom, so you can't really have it both ways.

[1] I would love to see a programmer's bill-of-rights that guaranteed a developer the ability to reuse any code that they'd ever written that didn't include any actual business or trade secrets. I once wrote an awesome string class for one employer that was even actually open source, but that was licensed in such an annoying proprietary manner that, even though I can still legally have and use the source code, I can never redistribute the source code. The company made games, so there was nothing at all about the string class that anyone would ever have cared about in a business sense.

Re:Why I am pro-GPL by chongli on Tuesday July 21, 2015 @02:41PM (#9924668)
For that to be true I would have to lose something I already possessed.

It's important to recognize that software -- all software -- is subject to network effects. The more popular a piece of software is, the more work is likely to go into it, more features added etc. If your favourite MIT-licensed software gets forked by a proprietary company and the proprietary version eclipses the original in popularity, you are very likely to be deprived of future support. In a way, software is analogous to a river: it's important to preserve everybody's access not just to the part of the river they live near but also its entire length upstream and downstream.

Re:Why I am pro-GPL by SomeCallMeTim on Tuesday July 21, 2015 @07:27PM (#9926638)
The opposite has been the case, though, in practice: When using MIT-licensed software that's popular, proprietary software companies have been happy to contribute back upstream, because it reduces their maintenance requirements.

And since when does a for-pay piece of software eclipse the original free version in popularity? If it did happen, then I'd assert that the "proprietary company" must have done a lot of work to make that possible. In that unlikely case, they must have invested a nontrivial amount in the creation of a powerful tool, and they deserve the profits it generates.

A far more likely scenario is that a proprietary company forks an MIT-licensed project, does something creative with it, sells it to a few people, and then the open-source community would copy the cool features and add them to the MIT project. The actual code to a new feature is typically not as hard to create as the design of the feature, which has already been done by our hypothetical proprietary company. Then the company will need to innovate again to stay relevant, and the free project can copy those features as well.

A healthy ecosystem can include some companies that don't share. It's all part of the network effect. If you can cite any situation where a community surrounding a free software library or other product has been killed or even harmed by a piece of proprietary software that is based on the same code, then you might have a point, but I don't think it's happened.

It DOES happen that proprietary software runs circles around the equivalent free software (Adobe Photoshop, for instance), but that's not because the for-pay software is stealing free code. It's because when you have hundreds of full-time developers you can produce a lot more than the same number of people can do in their spare time. And when those full-time paid developers can contribute to open source (as is frequently the case with MIT/BSD licensed projects), those open source projects flourish as well. Again, see LLVM/Clang.

Re:Why I am pro-GPL by marrs on Tuesday July 21, 2015 @10:27PM (#9927374)
But all of the examples you cite (with the exception of Photoshop) are used by developers. The article was talking specifically about serving the interests of users of applications.

I actually think you chose a bad example with the Adobe suite. Not one of the creative apps runs on Linux, I need an internet connection to keep the DRM system happy, and I have no guarantee that I will be able to open a PSD/AI/etc that I created 10 years ago on an older version of the software - a major concern for a serious amateur.

Re:Why I am pro-GPL by SomeCallMeTim on Wednesday July 22, 2015 @01:53AM (#9927936)
>I actually think you chose a bad example with the Adobe suite.

It's actually a perfect example:

* Any DRM it has obviously is annoying and could prevent you from using a valid copy (though I've never seen it not work).

* It's crazy expensive.

* Its UI is annoying.

And yet it's by far the most used piece of software when it comes to editing photos (with the possible exception of Adobe Lightroom).

FWIW, PSD is a pretty well standardized file format, and files created in older versions of PhotoShop have always reliably worked in newer versions of the app. It's the other way around, especially if you're using transformations that don't exist in the older app, where you most frequently encounter problems. Which means that if you don't pay their ongoing extortion fees, you might end up getting a PSD that you can't open because of some new feature the older app doesn't support.

Yes it's annoying. But it's also hands down the best, and no professional graphic artist would be taken seriously without it. Gimp doesn't even come close in functionality -- but even worse, the various tutorials and scripts you can follow or acquire for PhotoShop don't work in Gimp.

>The article was talking specifically about serving the interests of users of applications.

Sure it was, but in my example I point out one of many apps that is vastly superior to its open source equivalents, and yet it is the one that serves users the best. Yes Adobe extorts money from those users. Yes it would be nice if it were just open and free. But the reason that Adobe can make software that is so much better is that it can extort that money from users.

So what good is the GPL in fighting apps like this? It accomplishes nothing with respect to large companies like Adobe, because they can just pay to reimplement what they need.

The argument is that the GPL will allow better software to be written with capital-f-Freedom than proprietary. That the GPLed libraries will grow in quantity and eventually outcompete proprietary tools. Other than developer tools (and precious few of those even qualify, honestly), name a GPL application that's better than its closed source rivals. Write a list of all of them that you can think of, in fact. If you hit a half dozen, I'd be surprised -- and there are dozens if not hundreds of solid proprietary packages that make the open source packages look embarrassingly bad by comparison.

Yes you can find GPL apps that are Good Enough for some purposes. I do know people who use and swear by Gimp, for example, or Inkscape. But except for people who use Free tools for philosophical (or financial) reasons, the vast majority of end users want the mainstream, proprietary software that for the most part works the way they expect.

Users are being better served by apps that work well and have the features they need. It happens those apps typically are proprietary. Some philosophies sound good on paper, but in reality fall apart. The GPL largely falls into that trap, IMO, except for the awesome developer tools that are available for free. And Firefox. I still like Firefox. :)

Re:Why I am pro-GPL by marrs on Wednesday July 22, 2015 @05:11AM (#9928477)
I'm sorry but PS is not vastly superior to Gimp; it's largely equivalent. PS has tools that Gimp doesn't have and Gimp has tool that PS doesn't have. Given the choice, I use Gimp over PS because of the reasons I mentioned in my previous post, and also because I find its UI to be much less obtrusive, and because I can't find equivalent tools in PS for the work I do.

I deliberately avoided comparing the 2 apps in terms of features in my last post to avoid the tit for tat that will inevitably follow.

PS is required by professionals because it is the de facto standard image editing tool and it's the one graphic designers learnt to use in school, and because once you've bought a copy you're locked in. Frankly, if XCF was the industry file format and Gimp was taught in school, Gimp would be the tool everyone uses.

Re:Why I am pro-GPL by SomeCallMeTim on Wednesday July 22, 2015 @02:06PM (#9931274)
I've used both, and Gimp falls flat in the implementation of the features that it does have. It's not about filling in boxes in a feature comparison table. It's about how well each key feature works. [1]

And that's where most open source software completely falls down, because getting UI and polish into an app takes tons of time and experimentation to get right. Open source apps typically get to 80% and leave it there. Problem is, the last 20% of UI and feature improvement typically requires 80% of the time.

But even that is irrelevant, as you point out, because PS is the de facto standard, and Gimp can't open a multi-layer PSD and be expected to render it perfectly if it uses any nontrivial effects.

[1] Gimp seems to still be missing "adjustment layers," which I swear are used in 95% of the nontrivial tutorials I've seen for PhotoShop. I'm sure you can work around that, but that is a key feature of PhotoShop. Just because you don't find a feature important doesn't mean it isn't used by 90% of graphic professionals who use PhotoShop.

Re:Why I am pro-GPL by marrs on Wednesday July 22, 2015 @06:11PM (#9932717)

    I've used both, and Gimp falls flat in the implementation
    of the features that it does have.
I've also used both, regularly and for many years, and my experience is the opposite. As I keep saying, Gimp's UI and portability is what makes me keep using Gimp despite also having Adobe CC installed on my workstation.

    And that's where most open source software completely
    falls down, because getting UI and polish into an app
    takes tons of time and experimentation to get right.
I could just as easily say that this is where proprietary software falls down because software vendors sell their wares on features, not polish. As a professional software engineer, I know this first hand. PS continues to get feature after feature but its basic rectangle select tool is still a complete pain to use. Last time I checked, the Gimp team flat out refused to add support for 3D rendering. It took them along time to come round to the idea of adding vectors.

Actually, if you look at Gimp's development history, you will find that their approach for a long time now has been to work very hard on making the features they deliver as powerful and usable as possible.

This is partly why features are added so slowly. The other reason is because the development team are a handful of people who work on the tool in their spare time.

Yet despite this, they have built an excellent image manipulation tool in Gimp itself, they've developed the GTK+ UI toolkit that is the backbone of the excellent Gnome and XFCE desktop environments and countless applications. They've also developed the excellent GEGL library, the non-destructive rendering engine built precisely to enable adjustment layers (or their equivalent) in Gimp that you can't live without, which in the meantime has enabled the rapid development of Darktable, a very capable alternative to Lightroom.

In a futile attempt to keep this conversation on topic, I'll just point out that both GEGL and GTK are licensed under the LGPL, while Gimp and Darktable are both licensed under the GPL.

    Just because you don't find a feature important...
That's got nothing to do with it. I started working with Gimp because it was the only tool that ran on Linux that was capable enough to do what I required.

A user of a tool like Gimp or Photoshop makes the application work for him. Before adjustment layers existed, Photoshop users duplicated layers and blended them with the original to get the flexibility they required. I do the same in Gimp. As Gimp introduces more powerful features, I will take advantage of them.

Re:Why I am pro-GPL by baddox on Tuesday July 21, 2015 @02:20PM (#9924500)
It's the same kind of logic that the RIAA would use to conclude that my downloading a terabyte of music is equivalent to my stealing x trillion dollars from the record labels, regardless of whether I ever would have spent money on the music (or whether I ever even listen to it). It is, simply put, the logic of intellectual property laws. It's why I don't like intellectual property laws or things that rely on them (like the GPL).
Re:Why I am pro-GPL by marrs on Thursday July 23, 2015 @05:13AM (#9934706)
All software licenses rely on them. Copyright and patents are the only provisions under the law for licensing software, and both are used.
Re:Why I am pro-GPL by superuser2 on Tuesday July 21, 2015 @02:04PM (#9924363)
>depleting the community of improvements to the work they have made freely available under good faith.

You pretend those improvements would happen anyway. In RMS's world, proprietary software is not a business. The only way those improvements get created are

1) People individually fix their own problems and support their own use cases. Then boring, unsexy problems that no one is passionate about don't get solved. See: Linux desktop.

2) Businesses perform the least amount of development they can as a cost center; their actual business is consulting.

3) Some wealthy, benevolent patron lights money on fire so that the engineers making that software can keep warm.

Re:Why I am pro-GPL by dllthomas on Tuesday July 21, 2015 @02:23PM (#9924532)
Listing "Linux Desktop" as a problem unsolved because of a lack of sex appeal is bizarre. It has long seemed to be treated as "sexier" than it (to my mind) has deserved, and a tremendous amount of work has gone into a plethora of projects in this area.

Moreover, in my experience it has always been basically solved (handwringing articles notwithstanding). I wouldn't be surprised if a part of that has been my needs being unusual, though.

Re:Why I am pro-GPL by dzsekijo on Tuesday July 21, 2015 @04:24PM (#9925506)
> even RMS and the FSF use the more permissive LGPL for some of their work, most notably GNU Readline

"Readline is free software, distributed under the terms of the GNU General Public License, version 3" -- https://cnswww.cns.cwru.edu/php/chet/readline/rltop.html#Int...

Re:Why I am pro-GPL by thegeomaster on Tuesday July 21, 2015 @09:35PM (#9927192)
Oh, it was a slip of the tongue---I was thinking of this essay [1], and remembered it mentioning Readline and GNU libc, but for some reason thought that Readline was LGPL and libc was GPL (when the opposite is true and indeed makes way more sense).

[1]: http://www.gnu.org/licenses/why-not-lgpl.en.html

Re:Why I am pro-GPL by phkahler on Tuesday July 21, 2015 @02:04PM (#9924357)
>> I'm not yet convinced that MIT-like, BSD-like, and Apache-like are any worse at perpetuating user freedom, and may in fact be far better at perpetuating user freedom due to their greater acceptance.

Just try to get source code to any of the Apple or Microsoft OS parts that were BSD licensed so you can tweak them. Then come back and tell me how free you feel. I know you probably don't have a desire to change most of that, but my point is that you can't - for the parts that were changed from their BSD origins with no source released.

Re:Why I am pro-GPL by 0x09 on Tuesday July 21, 2015 @04:58PM (#9925761)
>Just try to get source code to any of the Apple or Microsoft OS parts that were BSD licensed so you can tweak them.

The bulk of projects available on opensource.apple.com are not GPL, including not least of all the kernel.

Anecdotally I have personally used the BSD-licensed file_cmds source package to fix some birthtime-related behaviors in cp, mv, and touch that I didn't like.

Re:Why I am pro-GPL by liviu- on Tuesday July 21, 2015 @01:39PM (#9924129)
>Many people disagree with me on this, but their disagreement usually comes down to "the GPL is best for user freedom because it was created for user freedom and RMS is talking about user freedom."

I don't think there's a need to create weak straw arguments, when an obvious argument is that GPL forces companies creating new products based on GPL-licenced software to open-source these products, thus aggressively perpetuating "user freedom". This may or may not be efficient in the long term, but I don't think the answer is very clear cut with the current knowledge base.

Re:Why I am pro-GPL by epistasis on Tuesday July 21, 2015 @01:53PM (#9924278)
I didn't mean to create a straw man, and I kind of intended exactly what you say there (if I'm understanding you): being "aggressive" means that it does the most for user freedom. I like your terminology better though and will use it in the future.
Re:Why I am pro-GPL by 0xdeadbeefbabe on Tuesday July 21, 2015 @02:58PM (#9924821)
> I don't think there's a need to create weak straw arguments, when an obvious argument is that GPL forces companies creating new products based on GPL-licenced software to open-source these products.

The obvious argument is that several people disagree with you on this (see the comment about linux being GPL or using GPL software at a bank.), so the GPL is not serving its purpose because people don't understand its purpose.

Re:Why I am pro-GPL by llllllllllllll on Tuesday July 21, 2015 @02:59PM (#9924828)
As far as i know Apache License, Version 2.0 is considered a free software license. To quote from gnu.org "This is a free software license, compatible with version 3 of the GNU GPL." source: http://www.gnu.org/licenses/license-list.en.html
Re:Why I am pro-GPL by clacke2 on Wednesday July 22, 2015 @04:32PM (#9932124)
Nobody is questioning that ASL2, MIT, BSD, Expat etc are free software licenses. The thesis is that they are not always as good as e.g. the GPLv3 at spreading lasting user freedom.