I've posted another response in the Cato Unbound online debate over the impact of Lawrence Lessig's Code and Other Laws of Cyberspace upon the book's 10th anniversary. You will recall that I went fairly hard on Prof. Lessig in my essay, "Code, Pessimism, and the Illusion of 'Perfect Control,'" and Lessig responded with a counter-punch that went after me for it. I respond in a new essay about "Our Conflict of Cyber-Visions." In the piece, I address Lessig's assertion that I just didn't understand the central teachings of Code, as well as his reluctance to accept the "cyber-collectivism" label that I affixed to his book and life's work. Again, please hop over to Cato Unbound for my complete response.
But one thing from the essay that I thought worth reproducing here is my effort to better define the key principles that separate the cyber-libertarian and cyber-collectivist schools of thinking. I argue that it comes down to this:
The cyber-libertarian believes that "code failures" are ultimately better addressed by voluntary, spontaneous, bottom-up, marketplace responses than by coerced, top-down, governmental solutions. Moreover, the decisive advantage of the market-driven approach to correcting code failure comes down to the rapidity and nimbleness of those response(s).
What concerns me about the way Prof. Lessig approaches these issues in Code and in his subsequent work is that he is far too quick to declare the debate over by labeling short-term code hiccups as sky-is-falling market failures. The end result of such myopic techno-pessimism is the inevitable call for governments to intervene and "do something" to correct supposed code failures. The cyber-libertarian instead counsels patience. Let's give those other forces -- alternative platforms, new innovators, social norms, public pressure, etc. -- a chance to work some magic. Evolution happens, if you let it.Moreover, if you are always running around crying "market failure!" and calling in the code cops, it creates perverse marketplace incentives by discouraging efforts to innovate or "route around" bad code or code failure. We don't want the whole world sitting around waiting for government to regulate the mousetrap to improve it or even give everyone better access to it; we should want the world to be innovating to create better mousetraps! To reiterate a key point I already stressed in my original essay: One need not believe that the markets in code are "perfectly competitive" to accept that they are "competitive enough" -- or at least, better than regulatory alternatives.