Racing the Beam
Racing the Beam: The Atari Video Computer System is a book by Ian Bogost and Nick Montfort describing the history and technical challenges of programming for the Atari 2600 video game console.
Stats for nerds
39recommend
58mentions
48people
2010–2026years
81% recommend19% neutral
Mentions per year
What Hacker News says
- I'm reading through the comments here before reading the actual Atlantic story, so I didn't see the author's name until you mention it:
> Bogost's statement is akin to calling the Amiga 500 the only home computer to be called beautiful.
Oh! That's Ian Bogost, who is a great writer of how our relationship with technology can evoke truth and beauty. The canonical work is his deep dive on the Atari 2600 and the early 1980s revolution "Racing the Beam":
https://en.wikipedia.org/wiki/Racing_the_Beam
Bogost wrote a number of books while working with MIT, arguing that video games were a new medium of communication back when that was a controversial point of view.
(I will need to re-subscribe to The Atlantic at some point. It seems churlish, but it's been an expensive year...)
- "Racing the Beam" is a great book by MIT press that covers the specifics of the Atari 2600 platform. The 2600 sparked a number of innovations _largely because of_ the limitations of the platform forces you to think outside the box.
- For anyone interested in the general topic, highly recommend https://en.wikipedia.org/wiki/Racing_the_Beam
- Nope. I'd go with anything from MIT. Racing The Beam and I Am Error were transcendental for me. Some stuff from Boss Fight books is absurdly good. Final Fantasy V immediately comes to mind.
- Hardware sprite systems such as the Atari 2600 did not have any VRAM.
The 2600 had 128 bytes of RAM. It supported a small number of fixed sprites. These were implemented by setting the X and Y coordinates in registers; as the scan-out of pixels passed that point, it would switch to drawing in the sprite color if a pixel was present at the bit position in the sprite.
It was possible to count how far down the screen the scan-out had got and re-use a sprite that had already been used above, to get more than the allowed number of sprites.
See the book Racing the beam for a lot more detail.
Edit: however this WAS a VRAM system. Seems to have added a dedicated shift helper but is still using blitting to VRAM. See "game timing" section of OP page.
- I'd be very interested to hear of other books and articles like this, too.
Edwin Hutchins's Cognition in the Wild is one of my favorite books. It's very technical and ethnographic, but less historical. It doesn't deal with code, but that's because it's about the nitty gritty of navigation on a Navy ship (pre digital computing), and (here's the historical aspect) it compares this to some traditional Polyponesian navigational practices.
The closest thing off the top of my head are titles in MIT Press's Platform Studies series, like Racing the Beam, about the Atari 2600, which is historical and technical. https://mitpress.mit.edu/9780262539760/racing-the-beam/
Maybe Casey O'Donnell's Developer's Dilemma? https://direct.mit.edu/books/monograph/4469/Developer-s-Dile...
If you make a Venn diagram with history, ethnography, technical details, and code as different circles, the central intersection may not be huge, but I think there may be a lot more if you remove some of the constraints. But I want to see more work at this intersection, and I hope more people do it.
