Game Development Then vs. Now: 512KB vs. 100GB
Description
This is another 'Swole Doge vs. Cheems' meme, this time comparing 'Dev back in 1996' to 'Dev in 2020'. The left panel shows a muscular Swole Doge wearing glasses and a 'GAME FREAK' t-shirt, holding a Pokémon Red cartridge for the Game Boy. The caption reads, 'I just fit Pokemon Red in 512KB'. This highlights the incredible feat of engineering required to fit a full-fledged RPG into such a small amount of memory. The right panel shows the smaller, crying Cheems dog wearing a t-shirt with the JavaScript 'JS' logo, sitting in front of a laptop. The caption reads, 'Hemlp, CALL OF DUTY USES 100GB>'. This humorously contrasts the resourcefulness of past developers working under extreme hardware constraints with modern developers who work with an abundance of resources, yet applications and games have grown to enormous sizes. It pokes fun at the perceived lack of optimization in modern software development
Comments
7Comment deleted
In 1996, we debated every byte. In 2020, we just add another 8GB of RAM to the minimum requirements
1996: “We shaved bytes off sprites to slip Pokémon into 512 KB.” 2020: “Sure, Call of Duty ships at 100 GB - but hey, at least my 3 KB config file pulls the entire Chromium build system in post-install.”
Back then we optimized for cartridge ROM limits; now we optimize for how many node_modules folders we can fit on a 2TB SSD before running out of inodes
Back when fitting an entire RPG into 512KB required actual engineering prowess and bit-level optimization, versus today where we casually npm install 300MB of dependencies just to center a div - and somehow the game that fits on a Game Boy cartridge is still more fun than the one requiring a dedicated SSD
1996: fit Pokémon in 512KB; 2020: 100GB of assets and 700MB of node_modules - we traded byte squeezing for dependency graphs and now the optimization is buying a bigger SSD
Pokémon Red packed a universe into 512KB; modern CoD's JS sourcemaps alone could fill the entire Game Boy library - tree-shaking optional
1996: bank‑switched tiles and hand‑packed ASM; 2020: 80GB textures, a 20GB day‑one patch, and a 200MB JS bundle just to render the progress bar