Remember the four freedom free software gives you: (0) running it for any purpose, (1) modifying it, (2) re-distributing it as is, and (3) re-distributing it modified.
With GPL, freedoms (2) and (3) can only be enjoyed at one condition: giving to those who receive the software the exact same freedoms you enjoyed. In other words, you shall not make your users less free than you are already. This is a long standing principle: one's freedom shall stop at others'.
I argue that the GPL merely forces you to respect that principle (it will be very hard to convince me otherwise). If you don't like that, I will be forced to question your morality.
I do think that the rhetoric (including the "four freedoms") is nonsense that could be left by the wayside with no harm, and possibly even improve it. That's the part about the GNU GPL and the FSF that I can't stand: don't try to tell me that this is about freedom. Tell me that this is about building a base of code that requires share-and-share-alike behaviour and that you're doing it because you think it will produce a richer environment. I may not agree with you, but at least I'll respect your stance.
If I want to restrict others use of my software in a way that they have to grant others the exact same rights that I granted them in the first place, then I will happily pick the GNU GPL or some other license that achieves the same thing, because that's what I want in that case. If I don't want to restrict others use of my software in any way, I will pick something much less restrictive (such as the MIT or BSD licences). If I want something in-between, I will choose an in-between license like the MPL or the LGPL. But in no way will I pretend that my application of restrictions is increasing freedom. It's the restrictions I'm choosing for the software I'm writing. No more, no less.
It restricts you from using software to build non-GPL software (including BSD-licensed free software), but it prevents software from being "taken private" by commercial developers.
I (again) don't so much care about the ethics (BSD's just fine) as I do about the commercial impact. The GPL is far, far more author-friendly than the BSD license is.
When I want to force others to share code that I have written, I will choose the GNU GPL or something very like it. If I don't care what others do with code, I will release it under a much less restrictive license.
Please don't be sloppy. It spread fallacies.
The GNU AGPL has even a lesser conditional trigger, access over a network.
What neither the GNU GPL nor the GNU AGPL require under any circumstances is contribution of modifications upstream or global sharing. You are only required (when the conditions kick in) to share your source with those who use your GNU {,A}GPLed software and not restrict them from modifying and sharing the source.
My shorthand statement to which you objected was incomplete, but definitely not incorrect. All forms of the GNU {,A,L}GPL have certain conditions in which you are required to make available the source and any modifications you have made to those who have obtained your software under such a license. (Of course, this also only applies to downstream authors and users; the original authors are under no such obligation.)
I feel that many people take it at face value and actually think that "the GPL forces to share modification", unconditionally.
If you use GNU licensed software, you are required to give out all of your changes to anyone that asks. In addition to this, anyone that requests the source can just as easily start sharing it and all of your modifications for free.
It sounds like you are getting annoyed because people aren't stating the obvious.
If I am a downstream ISV that has code under the GNU GPL because of upstream incorporation and sell my software to users, only those users I sell my software to may legitimately ask for a copy of the source. I cannot restrict them from giving it away or sharing it, but I don't have to honour all requests for the source and my modifications—just the ones from people I've distributed the software to.
Most businesses that use GNU GPLed software choose to either link to the upstream and host local patches, or host their custom distribution entirely, effectively giving the software away to everyone. They aren't required to do so by the terms of the license.
So, I am getting annoyed because you (and many others) don't understand the GPL. Go read it.
The disconnect the GP has is that the GNU GPL is based on freedom, yet it places significant restrictions on what you do with the software under the GPL. It's a fine license, but calling it "more free" is nonsense.