From Stallman to Lessig to Keen

Based on a Mar. 9th lecture by Gearóid Ó Súilleabháin

Another Richard Poynder interview that jumped out at me was the 2006 conversation with Lawrence Lessig, leader of the Free Culture Movement and co-founder of Creative Commons, who was mentioned in less than glowing terms by Richard Stallman.

Lawrence Lessig

Lawrence Lessig
Source: Wikipedia

Lessig is generous in citing Stallman and the Free Software Movement as key influences on his book “Free Culture”. Stallman is less so, noting in the Poynder interview problems he has with some Creative Commons licensing, and expressing the view that Lessig’s book shows him to be “less ethically firm”. The disagreement appears to reduce to Stallman’s insistence that people have a fundamental right to copy creative works while Lessig argues for a more nuanced position.

The Cult of the Amateur

Source: Wikipedia

It is therefore perhaps a little odd, given Stallman’s overt disappointment in Lessig’s failure to be absolutist, to read Andrew Keen’s criticisms of Lessig in “The Cult of the Amateur”. “A fronte praecipitium a tergo lupi” Lessig might have been thinking in reading that he and “cyberpunk William Gibson laud the appropriation of intellectual property.” But Lessig is a law professor and more able than most to defend himself, which he does quite comprehensively in a May 2007 post on his own site. Lessig suggests the Keen book can only have been intended as masterful “self-parody” and is “riddled with falsity”, errors he subsequently proceeds to parse in detail.

That said, I must confess to still preferring Keen’s take on amateurs.

Master of the Recursive Acronym

Based on a Mar. 9th lecture by Gearóid Ó Súilleabháin

Richard Stallman, progenitor of the Free Software Foundation (FSF), founder and lead architect of the GNU project (GNU’s Not Unix, hence the title of this post), and author of the widely-used GNU General Purpose License dubbed “copyleft”, does not, on further reading, appear much fond of compromise.

Richard Stallman Source: Salon.com

Richard Stallman
Source: Salon.com

A 2002 Salon.com article, Code free or die, reviewing a biography of Stallman, celebrates his stubbornness in stating that “his single-minded commitment and brutal honesty are refreshing in a world of spin-meisters and multimillion-dollar marketing campaigns”. Linus Torvalds, author of the Linux kernel (I will not address the GNU/Linux naming controversy here), indicates in a blog post that he is not a fan of Stallman because he doesn’t like “single-issue people” and he doesn’t think “that people who turn the world into black and white are very nice or ultimately very useful.”
Eric S. Raymond, co-founder of the Open Source Initiative (OSI), in a piece titled Shut Up And Show Them The Code, rejects Stallman’s rhetoric, claiming that OSI’s tactics work while FSF’s don’t, and that the excellence of open source software is a “more persuasive argument for openness and freedom than any amount of highfalutin appeal to abstract principles”.
But then Stallman too has plenty to say on what he sees as clear distinctions between free and open source software, noting on the gnu.org site that “Free software is a political movement; open source is a development model.”

Richard Poynder

Richard Poynder
Source: richardpoynder.co.uk

Journalist Richard Poynder’s superb interview with Richard Stallman is one of several of his Basement Interviews available online. The 2006 interview provides insight into Stallman’s combative nature and throws up gems such as “I don’t want to answer that question. I don’t like being handed a quotation and asked to utter it.” I strongly recommend that you download and read the interview in its entirety (available as a PDF from Poynder’s site or in text form here) as it contains Poynder’s detailed background and explanatory notes which are an education in themselves.

Stallman’s TEDxGeneva 2014 talk “Free software, free society” is worth a watch:

and early on includes a simple explanation of his four software freedoms:

  • 0: to run a program for any purpose.
  • 1: to study how a program works, and change it to make it do what you wish (requires the source code).
  • 2: to redistribute copies.
  • 3: to improve a program, and release your improvements (requires the source code).

I love the zero-based numbering.