Tom` said:
Well, yes and no - one of the major ideas I'm trying to get across is that a piece of artwork (or a movie, or a piece of literature) is its own source code - if I want to modify it, I can do so directly.
I don't agree with you, particularly in the case of movies. Even with literature you could argue that by not distributing a CD with a .txt of the book (or somehow making it readily available) the author is discouraging people from modifying it.
Tom` said:
Taking the literary example further, there's been for years an ongoing debate over the legitimacy of fanfiction - a debate which was stirred up recently when author Diana Gabaldon posted a screed on her blog which condemned the practice of writing fanfiction in strong terms. This upset quite a lot of people, because the default position, with more or less legal support depending on jurisdiction, is that fanfiction is perfectly legal and ethical (since for most Berne Convention signatories, ideas are not copyrightable - just specific descriptions of those ideas). Fanfiction clearly labeled as an independent work and not commercialized is tolerated by the vast majority of authors; some even encourage it, often under a Creative Commons license.
Fanfiction is not a modification of a work, it's a borrowing of certain elements in an otherwise new work, elements generally regarded as relatively abstract and under fair use. It's more akin to being inspired by the user interface of a program than forking its source code. If you took a book's text wholesale and modified some part of it and redistributed it I think the response would be very different from what you describe. The term you'd be met with is "plagiarism", which is not exactly heralded by the creative public, although I can't speak for yourself nor Mr. Stallman.
Tom` said:
Proprietary software, on the other hand, inherently restricts this kind of usage. A book, a movie, or an artwork is not comparable to a compiled binary, because that is only understandable to a computer - and moreover, any of those things are invariably distributed in a "finished" state.
A movie is not understandable by a human, it's understandable by a DVD player, projector, computer, etc, in a similar way a program is. You can sort of eventually edit a movie, in the same way you can resource hack and eventually reverse engineer a program, but you're at a substantially disadvantage compared to the original authors of the work. A particularly fitting example here would be that of a 3D movie.
Historically a lot of software HAS shipped "finished" (not perfect - but how many movies et al are? Of course we get things like director's cuts too..) The industry trend of releasing broken things is another issue, although admittedly it's difficult to escape this with as complex as software has become.
I'm not arguing that software shouldn't be fixed, but I don't see how that makes it immoral for software to be released w/o providing the end user a means to fix it. And honestly, I don't think the real thrust of FSF's zeal is that pragmatic, I think it's all a question of injustice. I think when rms couldn't fix those drivers his response wasn't that it'd be better if he had the source code to the drivers (mind you, the original authors fixing it wasn't an option, and I think that this is indicative of how he views a lot of things, a kind of superiority complex/control issue that for instance leads him to expect all useful software to eventually be under GNU), but that this is "wrong" and an entire worldview needed to be erected to counter it.
Tom` said:
Software, on the other hand, frequently is not, insofar as bugs are fixed and new features added, and nowhere is this more important than in the case of an emulator.
edit: and this, more than anything else, is why I would be very unlikely to pay for an emulator, unless I was certain it would either be perfectly functional (highly compatible, smoothly playable if not actually full-speed) or that development was and would continue to be ongoing, and I would receive updated versions at no additional charge.
Sounds entirely reasonable to me to not pay for something that doesn't promise to stay on top of fixing things, or isn't "good enough" from the start (most emulators won't approach perfection).
However, I do think that for some emulators (definitely not all, many prove the exact opposite) they benefit MUCH more from having their original authors focused on working on them than from being open source. So take your pick - if the original author(s) abandons the emulator then you'll want it to be open, but sometimes you'd prefer they stick with it. This is more true for embedded programs than PC ones, and emulators for handhelds falls more under the embedded realm.
Also, if someone is charging $3 for an emulator that may not be perfected, but is also the only game in town (and may be indefinitely) then while you may not put down the negligible amount of cash on principle most will basically choose to be at the developer's mercy.