5 ms·
I don't know, it's a bit like taking a screenshot of a text file, and wondering why the screenshot is 64k and the text file is only 500 bytes (or whatever).
by larrik 11y ago
I don't know, it's a bit like taking a screenshot of a text file, and wondering why the screenshot is 64k and the text file is only 500 bytes (or whatever).
- joezydeco 11y agoThat's a much better analogy. I was expecting more of a realistic explanation about how the NES puts up the frame without a frame buffer. This falls into a mess about graphics compression, which is kind of irrelevant.
- corysama 11y agoYou would like this: "How 'oldschool' graphics worked Part 1 - Commodore and Nintendo" https://www.youtube.com/watch?v=Tfh0ytz8S0k https://www.youtube.com/watch?v=Tfh0ytz8S0k
- joezydeco 11y agoI prefer Montfort and Bogost's Racing the Beam from MIT Press: https://mitpress.mit.edu/books/racing-beam https://mitpress.mit.edu/books/racing-beam
- kozukumi 11y agoIndeed. I also didn't much like the comparison to the .kkrieger demo saying it was "only" 24KB more. Sure the raw exe is but it still needs GB of memory and a crazy fast CPU to do all the content generation at runtime. He also used inconsistent mb/MB, etc. which always gets on my nerves in a technical post but now I am just being an asshole at it is 2am here ;)