A Short Interview with John Carmack

The Guardian Gamesblog had the chance to pick John Carmack's brain about mobile gaming's first official doom title: The Doom RPG. From the article: "Q: On your blog you talked about getting into Java programming as a means of resetting some assumptions and habits after working on Quake III. So did Doom RPG help? How? A: It wasn't so much the Java aspects as the mobile platform that is the diversion. It has been worthwhile, but I didn't get to go all that far down the detour before my primary responsibilities asserted themselves. I did three major blocks of coding on the project and regular design review meetings, which was all I could spare the time for. The crew at Fountainhead did a great job of following up on the direction and turning my rough project into a polished product."

Comments

Layer on Layer on Layer on Layer on...

[MiceHead]

Carmack's last blog entry, waaaaay back in March, goes into further detail about why it's tough to optimize for mobile platforms:

Gamers generally have poor memories of playing over even the highest speed analog modems, but most of the problems are due to having far too many buffers and abstractions between the data producers/consumers and the actual wire interface. If you wrote eight bytes to the device and it went in the next damned frame (instead of the OS buffer, which feeds into a serial FIFO, which goes into another serial FIFO, which goes into a data compressor, which goes into an error corrector, and probably a few other things before getting into a wire frame), life would be quite good.

I'm interested in developing mobile games -- it seems like it's indie-developer friendly, as Palm OS was back in 2000. However, as Carmack suggests, developers are constrained by the architecture. Things like a 64k memory block limit (remember the days of 16-bit programming?) are a pain in the rump. Here's hoping for a good Mobile Python.