Slashdot Mirror
Will Stallman Kill the "Linux Revolution?"
frdmfghtr writes "The October 30 issue of Forbes Magazine has an article speculating that Richard Stallman's efforts to rewrite the GPL could threaten to 'tear it apart.' The article describes how the GPLv3 is expected to be incompatible with the GPLv2, causing trouble for Linux vendors such as Novell and Red Hat. The article wraps it up: 'And a big loser, eventually, could be Stallman himself. If he relents now, he likely would be branded a sellout by his hard-core followers, who might abandon him. If he stands his ground, customers and tech firms may suffer for a few years but ultimately could find a way to work around him. Either way, Stallman risks becoming irrelevant, a strange footnote in the history of computing: a radical hacker who went on a kamikaze mission against his own program and went down in flames, albeit after causing great turmoil for the people around him.'"
Linux is going to stick with GPLv2 regardless of what the FSF does with GPLv3. That has little to do with Linus disliking GPLv3, and much do to with not being able to track down all the contributors and get them to agree to a license change. GPLv3 is not going to cause any trouble for Linux vendors. It's certainly not going to "kill the Linux Revolution". There is nothing in GPLv2 or GPLv3 that prevents a Linux distribution from containing various programs under various licenses, just as Linux distributions today contain code under GPLv2, BSD, MIT, and other licenses. And GPLv3 doesn't make Stallman himself any more or less relevant that he's been in the past. The only point of bone-headed sensationalist reporting like this is to try to sell more copies of the magazine. Next month they'll tell us the GPLv3 will contribute to global warming, and the following month that it will promote slavery.
Many of us have already moved away from Linux to BSD. Besides the many technical advantages of FreeBSD, the portability benefits of NetBSD, the extreme security of OpenBSD, and the massive scalability of DragonFly BSD, we don't have to deal with unreasonable licensing nonsense.
If somebody wants to take BSD code, modify it and not release those changes, then so be it. It doesn't hurt the rest of us, as we still have FreeBSD, NetBSD, OpenBSD and DragonFly BSD to use. Beyond that, such use may make somebody else better off. Thus, there's a net benefit overall. We lose nothing, yet others gain.
And I'd be very happy if Microsoft were to use more BSD code in their products. Doing so would result in a vast increase in the quality of their codebase. That, in turn, will result in fewer infected Windows systems that send terabytes of spam to my mail servers. The less spam my servers have to filter, the more money I save in bandwidth and processing costs. I may even be able to reduce the number of mail servers I have.
I find it hard to take Frobes seriously when they start out by misrepresenting the postion of the person they are talking about (Stallman).
"Richard M. Stallman is a 53-year-old anticorporate crusader who has argued for 20 years that most software should be free of charge. He and a band of anarchist acolytes long have waged war on the commercial software industry, dubbing tech giants "evil" and "enemies of freedom" because they rake in sales and enforce patents and copyrights--when he argues they should be giving it all away."
C'mon, people! This is a Dan Lyons article. He's been writing anti-Linux FUD for years. Groklaw and /. have eviscerated this guy's credibility on this subject repeatedly (do a search, you'll see). Quoting him on this subject is like asking Bill Gates if he thinks Linux is going to beat Windows in the marketplace: you know the answer before you ask the question.
Because, all the fashionable slashdot trolling to the contrary, he's an eminently practical man. If he released it PD he knows someone would just grab it, modify it a little, and close it off. He knows this because he learned the hard way - this was done with much of his early work.
He'd like to change copyright law, but being unable at least for the moment to do that, he came up with a way to hack copyright law to serve his purposes instead.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
Let me see ... how many Ecumenical Councils were there? So the Nicene Council around 325 - oh, wait, the Nicene Creed was amended a little at the later Constinopolitan Council ... so it has only been unchanged in the last 1500 years. Besides the creed itself, they passed a whole lot of provisions of canon law. Then there were the provisions of the other councils, and the later Orthodox and Catholic Councils that still have force as canon law. The laws of England include provisions going back to the reign of Edward III (1300s) that are still in force (or were until recently). Hmmm Magna Carta - now there is a document to make your Constitution look like a juvenile.
History wasn't invented in America. Some places have been around longer, and have a longer tradition of unchanged principles. Jewish law goes back, in some matters, over 3,000 years. America is just a Johnny-come-lately in the world of legal history.
I am anarch of all I survey.
It was always that way. Killing is perfectly justified for a large variety of reasons in the Torah. Capital punishment is common, there are fairly complex rules for retribution, and plenty of times G-d Himself says "go out and win a glorious victory" if you read the assorted Prophets and Writings. If all killing were outlawed, there'd be a heck of a lot of contradiction here.
Murder, though, is unjustified killing. It breaks one of the Ten Commandments to pick a child at random and bash his head in. It does not break one of the Ten Commandments to kill your enemy in battle.
I prefer to reading which doesn't cause G-d to be commanding His people to break the Ten Commandments, personally.
For the nitpickers:
The Hebrew word in question is 'ratzach' (which is conjugated to tirtzach in the text; Exodus XX, 13). Modern usage (according to my dictionary) clearly indicates murder as the first definition, and 'kill' as secondary. There is another verb 'harag' which can also mean 'kill', unfortunately I'm not as up on my Hebrew, so I can't say for sure whether this word is: a) used for more general killing, b) used more for killing of animals, or c) a modern invention.