>This is how I really want to be build the app so the users
>don't have to track down anything else to get it to run.
I just want to voice my complete agreement with this statement and
stress its importance. One of my least favorite things about Mac OS
X, from a user perspective, is that suddenly nothing works without
downloading and sometimes compiling obscure libraries from the GNU
When I'm in pseudo-developer mode, this isn't a problem. Just
download and follow the instructions. But often, while the program in
question is designed for Mac OS X, the needed components aren't, and
I have to fight with them/translate instructions for another OS to
Mac OS X.
Contrast with Mac OS 9, where often the "worst" one must do to play a
game is download a self-mounting image file with some extensions in
it (which are often accompanied by a point-and-click installer).
This is probably OK for most of the people on the list, but when I
get into "user" mode (or "I just wanna play NOW!" mode) it is
absolutely intolerable and has made it so that I just give up on a
Eh, I think that came out more ranty than I wanted it to sound, but
basically, yes, it would be great if we could keep it so that the Mac
OS X build just requires the normal Marathon data files to play and
not any external libraries. The 200K or whatever of bloat is next to
nothing these days.
Matt Lee | PGP key available:
zebe@... | http://zebe.net/pgp.asc