FSF's Opinion of the Apple Public Source License
Stian Engen writes "Bradley Kuhn of the FSF does not recommend the release of new software using the Apple Public Source License (APSL) 2.0 despite its
newly accuired Free Software License."
← Back to Stories (view on slashdot.org)
Since when does the FSF recommend other software licenses then the GPL? Even the LGPL isn't recommended.
Its a hell of a lot better than the old license. And its not like developers working with Darwin have much of a choice. I mean, who is going to use the APSL on a non Apple derived product?
I guess that Michael needs to learn to review previous stories - this story, complete with the details about FSF approving but not recommending it, was covered in an article three days ago.
In any case, I can't really imagine the FSF recommending any license other than their very own GPL, now the darling of IBM and the open source movement in general. Not that it isn't deserving of this adoration, as it may have saved Linux from SCO.
But who really expects them to be Free?
RMS and the FSF. Then again, the GNU/Hippy crowd often reminds me of a greedy, petulent child. When MacOS was completely proprietary, Apple was evil for not letting the code roam free in wild fields as it is apparently entitled to. When Apple opened up some code, they were chastisted for not opening it in the manner that the FSF demands... err, politely asks. Now Apple has changed its license to appease the FSF, but the first thing the FSF does is spout off about how the changes aren't good enough, and even if they were Apple would still be condemned for not opening up all of OS X.
Frankly, I think Steve should tell RMS to shove it. Apple has already given back a lot of code (ZeroConf, KHTML updates, etc.), but the FSF is never going to be happy. Apple should just continue to make jobs for lots of developers and make quality products, be they proprietary or open source.
I find it incredible that all the posters to the SCO stories say how terrible the land grab is and yet here, the majority of posters are criticical of the FSF for endeavouring to prevent that kind of nonsense from happening again. I don't pay too close attention to people's usernames so there may be a completely different demographic contributing to both stories but I suggest that those posting here get out their history books and start reading. You may then understand why the "idealogy" of the FSF is so important and precious.
Hey buddy,
When a congregation collectively works together to feed the poor by cooking and delivering large amounts of free food, is that communism too? The restaurant owner next door might lose some business. How about when the congregation runs a car wash to collect money toward housing renovations for the poor? Is that communism? The car wash owner down the street might think so. Is it communism when individuals donate a few bucks after Sunday service? Isn't that -- by your line of logic -- communism too?
It's not though. Communism is -- by definition -- ideology enforced by governmental institution and bears no relationship to individuals, acting on principals of free association, freedom of speech, and freedom of commerce (in this case the freedom to donate one's time and effort) toward a collective goal. You're simply red baiting free software authors for committing acts of FREEDOM in a free society. It is my right to donate money to church, the ACLU, EFF, or - *gasp* - even the FSF. Just as it's my right to donate code under whatever license I might choose. A very different proposition from the government forcing me to give my code away under communism, or for that matter, a government which prevents me from giving my code away. In both cases, we're talking about government restricting individual freedom and rights to enforce a certain ideology.
Communism my ass.
--Maynard