Re: Why retroprogram?

> This always makes me wonder why people do such things. Why document the
> Tempest code? Why write new games for obsolete hardware? I'm not saying
> these activities are bad, but why do them?

I have quite a number of answers to this, in no particular order:

I'd like to program a game. For me, retroprogramming a game is a much more
achievable goal than writing a modern one. I've got 20k to work with. The
hardware is much simple to deal with. The results don't have to be as
spectacular (as far as graphics and sound, anyhow). It is just more
achievable to write something good on a simple box.

But in reverse, it is also challenging. You've charting a lot of virgin
territory and squeezing the most you can out of something that is
hopelessly dated by today's standards. Doing the research to get to point
X so you can go onto point Y. (Did I use "virgin" and "squeezing" in the
same paragraph?)

Retroprogramming has a major cool factor to it. Wrote a game? So what.
Wrote a game that goes inside a Star Wars cockpit? Cool!

It's taking something you like, and turning it into something you like
even more. Maybe adding value to something. Instead of having a "Dig Dug",
you now have a Dig Dug that'll also play X, Y, and Z. Maybe it's also a
bit of 'leaving your mark'.

There's also the recognition that goes along with it. Hey, take a look at
what this guy did! I got his ROMs and now my Pole Position acts like a
River Raid!
Received on Tue Sep 28 12:50:24 1999