Slashdot Mirror
Perens Discredits Mundie's Attack On GPL
SaxMan101 writes "CNET has an editorial from Bruce Perens that quite handily dismantles Mundies attack on the GPL and the Liberty Alliance. He takes the time to make YA strong argument for free software which he backs up with real numbers. Well said, worth the read."
If you drill down a bit you find this letter from a programmer that complains about Open Source. While I found it both sad and funny, it does shed light on how Microsoft and other commercial software vendors view the movement.
To summarize: OSS is a bad thing because if free software is available no one will want to pay for software, which will drive programmers out of work. OSS is good in that it establishes competition for Microsoft, but that competition is better done through litigation or other commercial software.
Applying this point of view to Microsoft is humorous, of course, considering what they did with IE.
I actually don't think the developer has a point, though. Open source software has created far more jobs than it took. Linux, Apache, and other free platforms and development tools have meant, in my experience, that corporations are financially able to deploy systems that would otherwise have been prohibitive. The spread of such tools has also increased the number of people who are exposed to them - how many people would be running personal Unix systems if they had to have commercial systems? These people are able to get jobs in IT they would otherwise not be qualified for, or perhaps even know about.
In any case, Perens' response likening software development and protective measures against open source competition to buggy whips (actually ice, in his analogy) is only half the story.
(email addr is at acm, not mca)
We are Number One. All others are Number Two, or lower.
--The Sphinx
While all the points he makes are true, and the economic beneifits of free software are obvious, that is not the primary moral justification for software being free. Repeat after me, "When software is free, the world is a better place."
Now, it stands to reason, that part of the world being a better place is certainly the economic benefit that free software provides to reduce operating costs. In fact, one could argue that if there were no such effect, free software wouldn't be too great a thing -- who'd want it if it had no value (rather like some excuses for programs I've seen)? And they'd be right. These are open source arguments, though, and miss the fact that freeing software not only results in lowered operating costs for businesses that use it, but it changes the every environment in which they operate.
There are two primary schools of economic thought: planned economies and free markets. Politically, you have the statists on one side and the libertarians and anarchists on the other. Proponents from both sides argue that "their" way serves to distribute scarce resources in the most effective way, and that's what we want, no? -- effective distribution of scarce resources.
Well, yeah, but that doesn't make the scarcity go away, does it? Oh sure, the technological advancements that lead to efficiency improvements do eventually trickle down to everyone so that certain scarcities are less visible, but that's just a kludge. Think water. Most cities have methods for distributing drinking water to the point that, although the amount of water available may remain the same, it hardly seems locally scarce, even though it may have come from far away.
Free software serves to reduce the scarcity of good code out there. It provides value without relying on scarcity as the source of that value. It is a threat only to those who seek to leverage their possession of a scarce resource for maximum value. Now, if that resource is naturally scarce, fine: once sold, it is gone. But if the resource is artificially scarce, you can manufacture more of it for no cost, and charge whatever the market will bear, for pure profit (until you saturate the market, that is, but time-limited use licenses take care of that "problem" -- Microsoft's latest licensing strategy). It gives the owner incredible power over society as a whole (until society revolts).
But it costs money to produce code! People can't afford to give it away!! Well, if they depend on making it scarce for their livelyhood, no, but that is a bootstrapping problem: you make something artificially scarce in order to deal with real scarcities in your life. You'd have to do this less if there were less scarcities to worry about (imagine if we had solar-powered food-generation machines). And indeed, some have managed to give code away. RMS has done this exclusively, though by living a rather austere lifestyle. His choice. Others give code away when they can afford to. Each such contribution changes our environment for the better. For hackers who breathe code, this is, of course, a godsend (RMS, an atheist, might not like that choice of wording -- "GPLsend" then). Perhaps that's why we like the GPL so much, even those of use that produce restrictively-licensed code for a living.
So, you don't need economic arguments to defend the GPL. It is as good and wonderful for the world as are the lack of patents on fire, wheels, and language. The only people who will criticize it are those that profit from the misery that scarcity brings.
You could've hired me.
You ARE right...but it's truely ironic.
MS is THE premiere player in trying to sell cheap/free until they get marketshare, then raise the price.
Here in Portland OR, MS convinced First Interstate Bank to install NT 3.11 instead of Netware in their new 3000+ employee loan center - and almost purely because it was cheaper than upgrading from Netware 3.X
The bank didn't have any serious tools (Sniffer etc) in the old environment, and the hardware was ancient. But the OS was going to save them like 20K+.
What most of the outside world didn't know, was that the network went down almost daily for months. The result was thousands of people sitting idle (a double drain - their getting paid, and NOT making money).
Finally, after coming hours from chucking the whole thing, the MS engineers finally called the ONE guy who wrote the TCP stack. After a short conversation, the MS programmer suggested an undocumented TCP stack option. All of a sudden, the SNA session timeouts just stopped.
The point? MS SOFTWARE was like 20K cheaper, but the whole experiement cost the bank like HUNDREDS OF THOUSANDS (possibly even millions) of dollars. Even without the NT problems, the costs were VERY substantial to switch vs. staying on Netware.
MS has used the "IT'S FREE" or "IT'S LOTS CHEAPER" approach more than I can believe - Office bundled with the OS, (Office 4.3/95) IE/OE, NT (early on), MS Windows Plus, Windows 2.X-3.X (Bundled with Windows).
BP may not have dealt with the entire problem, but frankly, the PHB's aren't looking at TCO. If they were, we'd have run screaming from IE/OE a LONG time ago. We'd have set ourselves on fire when we see the rising cost of Office (Now it's MUCH more expensive than before - un upgrade used to cost like $200, now it's like $400), and the moving platform of MS's site licensing (I forget what MS called it - I think it used to be License+, now Select something? Doubled and Tripled in less than 5 years - loss of concurrent licensing)
PHB's only see the INITIAL costs. If they are concerned about TCO, they will look at the HUGE problems with viruses, crashing boxes (Re-Image anyone?!) and lots of features that really waste time and aggrevate users. (Clippie Anyone? How about how Word decides how you REALLY NEED that numbered list done etc!)
Sure, it's difficult to learn a totally new platform. But I do think that the Linux platform isn't any more difficult to administer. Ever tried to figure out Active Directory - it's got me confused! [Grin] How about when Exchange just stops sending mail in or out, but everything LOOKS fine - but a reboot fixes it? What about when IIS gets remote rooted and you get to rebuild your entire server?
I don't think you were defending the MS status quo, but even if you were, I think that defending MS will be a loosing battle in TCO. Bugs and security problems seriously compromise the TCO calculations on ANY MS software.
Finally, TCO numbers are SO perfect for manipulation. Everyone can make TCO numbers say anything they want. It's like the 10 year USA Gvmt budget. You can CLAIM you know where things are going to be, but frankly, you don't have a clue. TCO is usually just a massive marketing ploy.
Cheers!
Have you considered being a technical writer or something? There are many ways that anyone can help.
Bruce
Bruce Perens.