I don't think you should just "drop it." I value having my thoughts challenged, though I do prefer it be done in a respectful way.
Snarkout wrote:RMS should keep his mouth shut sometimes- his type of "Freedom" means exactly jack shit when you are genuinely oppressed or are starving to death. Software freedom is only of concern to those who give a shit about "piracy" and things of that sort to begin with. It is a "designer" problem. When you can be shot for voicing an opinion "having access to the source code so you can tweak it" is a non-concern. When you live somewhere where *all* software is free because *all* software is pirated, "Freedom" is of little concern. "Free" is a laudable goal, but RMS needs to get his head out of the sand - it is a very minor concern for anyone who isn't among the world's most privileged. His constant blathering about his "Freedoms" as if they were essential human rights is short sighted at best. So, yes, while I agree that it would probably be a blow against "Freedom" if the OLPC XO ships with XP, I don't see it as affecting the "big picture" at all. Then again, I've often said that the idea of giving a computer to a starving or nearly-starving person is strange at best and insanity at worst. It's perhaps the most warped example of trying to solve social issues with technology I have ever seen.
Obviously people who are starving are going to have software freedom near the bottom of their priority list, and many of these countries have much bigger issues to deal with. But how does this make software freedom something we shouldn't care about at all? I don't see anyone honestly saying, "yeah, we have to set aside all the other issues of malnutrition, health, and oppression while we work on this software freedom thing." They just say that software freedom is the better option, and that they should use it on the XO instead of using proprietary software. I just don't see anything wrong with that.
Software freedom, to me, seems less a "designer problem" and actually a relevant concern in education. You see software freedom as mere "tweaking" of code, while I see an opportunity for kids to get their hands dirty and learn from examples, perhaps the best way one can learn things. If the kids are stuck learning one company's platform, using one company's tools, and will never see how it all works, you're necessarily limiting what they can learn. How could kids ever learn about basic OS and kernel level ideas if they're stuck with XP? There's an obvious con to going with proprietary software, so what gains do you achieve from it?
I obviously could be mistaken, but sticking kids with XP is a bit like teaching someone to drive a car and buy gas, but never letting them look under the hood to get a better understanding of how it all works. I can understand someone wanting to fight for people's ability to look under the hood and learn all they can.