@Sean Timarco Baggaley
No, there is more to it. When GPL v1 was written a bottom end Sun UNIX workstation retailed for more than $15000, and I think it did not include a C compiler. A lot of people who knew they could make their own got together and made GCC and other people made Linux and the *BSDs.
None of them wanted to see other people rape their work, or take their work and assume control of it - which is possible with a public domain release. Their work was not 'the commons', and they cared that it not become so. Thus the constraints built into the GPL.
The GPL does not stop a corp using GPL code: it requires only acknowledgment if the corp keeps it's changes private; it requires disclosure if the corp release it's changes. The GPL stops nobody from using GPL code, but it does stop corps using GPL'd code as a product of the commons.
At least in the USA there is the question of free speech. And in the USA 'free speech' is written with capital letters... IIRC there was a landmark court case in the late 1990's that established that software is speech, thus free from coercion. A gov't of the USA can no more than a corp in the USA restrict free speech.