Off-campus access
Using PhilPapers from home?
Click here to configure this browser for off-campus access.
- Scott Aaronson, Evolution of Mutating Software.We propose using random walks in software space as abstract formal models of biological evolution. The goal is to shed light on biological creativity using toy models of evolution that are simple enough to prove theorems about them. We consider two models: a single mutating piece of software, and a population of mutating software. The fitness function is taken from a well known problem in computability theory that requires an unlimited amount of creativity, the Busy Beaver problem. (Talk given Friday October 10, 2008 at the IBM Watson Research Center in Yorktown Heights, NY. The author wishes to thank his colleagues Charles Bennett and David DiVincenzo for their helpful comments.).
Similar books and articles
The “free” in “free software” refers to a cluster of four specific freedoms identified by the Free Software Definition. The first freedom, termed “Freedom Zero,” intends to protect the right of the user to deploy software in whatever fashion, towards whatever end, he or she sees fit. But software may be used to achieve ethically questionable ends. This highlights a tension in the provision of software freedoms: while the definition explicitly forbids direct restrictions on users’ freedoms, it does not address other means by which software may indirectly restrict freedoms. In particular, ethically-inflected debate has featured prominently in the discussion of restrictions on digital rights management and privacy-violating code in version 3 of the GPL (GPLv3). The discussion of this proposed language revealed the spectrum of ethical positions and valuations held by members of the free software community. In our analysis, we will provide arguments for upholding Freedom Zero; we embed the problem of possible uses of software in the broader context of the uses of scientific knowledge, and go on to argue that the provision of Freedom Zero mitigates against too great a moral burden—of anticipating possible uses of software—being placed on the programmer and that, most importantly, it facilitates deliberative discourse in the free software community.
It is not uncommon for students to try, and indeed to succeed, in buying the course texts used. This often makes a great deal of sense. But for this course, you must buy the textbook new . Here's why. The textbook comes with software that you will use to submit all of the course homeworks. The problem is that only one student can register the software , per book — period. So, if you buy the textbook used, not only do you run the risk that the software won't be intact, you will be unable to register the software and, therefore, unable to turn in your homework.
Computer software is written in languages like C, Java or Haskell. In many cases social software is written in natural language. The talk will explore connections between the areas of natural language analysis and social software.
This unique book presents a comprehensive and rigorous treatment of the theory of computability which is introductory yet self-contained. It takes a novel approach by looking at the subject using computation models rather than a limitation orientation, and is the first book of its kind to include software. Accompanying software simulations of almost all computational models are available for use in conjunction with the text, and numerous examples are provided on disk in a user-friendly format. Its applications to computer science itself include interesting links to programming language theory, compiler design theory, and algorithm design. The software, numerous examples, and solutions make this book ideal for self-study by computer scientists and mathematicians alike.
There has been a transition in the way software developers work. Mistakes in software have been treated as "normal" occurrences. "All software has bugs." However, software engineering is an emerging profession which as a profession has now said that a caviler approach to software errors is unacceptable. They have asserted a very strong ethical position in the Software Engineering Code of Ethics and Professional Practice, a position which mandates concern for all those affected by their work. The Code has several unique elements as a professional Code.
In defining the concept of software, I try at first to distinguish software from data, noise, and abstract patterns of information with no material embodiment. But serious objections prevent any of these distinctions from remaining stable. The strong thesis that software is pattern per se, or syntactical form, is initially refined to overcome obvious difficulties; but further arguments show that the refinements are trivial and that the strong thesis is defensible.
Software piracy has become recognized as a major problem for the software industry and for business. One research approach that has provided a theoretical framework for studying software piracy has been to place the illegal copying of software within the domain of ethical decision making assumes that a person must be able to recognize software piracy as a moral issue. A person who fails to recognize a moral issue will fail to employ moral decision making schemata. There is substantial evidence that many individuals do not perceive software piracy to be an ethical problem. This paper applies social exchange theory, in particular equity theory, to predict the influence of situational factors on subjects' intentions to participate in software piracy. Consistent with the predictions of equity theory this study found that input and outcome situational variables significantly effect a person's intentions to commit software piracy.
Claims about the potential of free software to reform the production and distribution of software are routinely countered by skepticism that the free software community fails to engage the pragmatic and economic ‘realities’ of a software industry. We argue to the contrary that contemporary business and economic trends definitively demonstrate the financial viability of an economy based on free software. But the argument for free software derives its true normative weight from social justice considerations: the evaluation of the basis for a software economy should be guided by consideration of the social and cultural states which are the ultimate goals of any economic arrangement. That is, the software economy should be evaluated in light of its ability to provide justice. We conclude with a discussion of possible avenues for reform.
Software is a ubiquitous artifact, yet not much has been done to understand its ontological nature. There are a few accounts offered so far about the nature of software. I argue that none of those accounts give a plausible picture of the nature of software. I draw attention to the striking similarities between software and musical works. These similarities motivate to look more closely on the discussions regarding the nature of the musical works. With the lessons drawn from the ontology of musical works I offer a novel account of the nature of software. In this account, software is an abstract artifact. I elaborate the conditions under which software comes into existence; how it persists; how and on which entities its existence depends.
Efforts to counter software piracy are an increasing focus of software publishers. This study attempts to develop a profile of those who illegally copy software by looking at undergraduate and graduate students and the extent to which they pirate software. The data indicate factors that can be used to profile the software pirater. In particular, males were found to pirate software more frequently than females and older students more than younger students, based on self-reporting.
Discussion of Scott Aaronson, Evolution of mutating software
|
|
There are no threads in this forum |
Nothing in this forum yet.

