The 1987 game "The Last Ninja" was 40 kilobytes
Remember when 'The Last Ninja' packed stunning graphics and sound into a mere 40 kilobytes? This Hacker News post marvels at the ingenious efficiency of 1980s game developers working under severe memory constraints. It sparks a nostalgic appreciation for resourcefulness and a critical look at today's software bloat.
The Lowdown
The story celebrates "The Last Ninja," a 1987 Commodore 64 game that achieved impressive isometric graphics and an iconic soundtrack with only 40 kilobytes of data, contrasting this sharply with the massive file sizes of modern applications and even static images.
- The original post expresses awe at the ingenuity of developers like System 3, Ben Daglish, and Anthony Lees, who created rich experiences within extreme technical limitations.
- It highlights the game's 40KB size in stark comparison to an average 400KB static image today, questioning how such feats were possible.
- The game was particularly praised for its visually appealing graphics and its highly acclaimed, memorable soundtrack.
This stark comparison prompts reflection on how far computing has come and what might have been lost in terms of optimization and resourcefulness as computational power became abundant.
The Gossip
Glorious Gaming Gold
Commenters fondly recall "The Last Ninja" and the golden age of 8-bit gaming, celebrating its groundbreaking graphics and iconic music. Many shared personal anecdotes and tributes to the era's creative genius, particularly composer Ben Daglish, marveling at the immersive worlds built under severe technical limitations.
Bloat Busters and Byte Battles
The discussion often pivoted to contemporary software development, with many lamenting the pervasive inefficiency and "bloat" in modern applications. Users contrasted current multi-gigabyte installations and memory footprints with the lean, highly optimized code of the past, prompting reflection on lost skills and the ease of ignoring resource constraints today.
Kilobyte Kinks and Context
Several commenters offered crucial context regarding the "40 kilobyte" claim, pointing out that this likely referred to the game's in-memory footprint on a C64, not its total storage size on disk or tape. While the actual media size was larger, it was still remarkably small, leading to discussions about the distinction between program logic and generated data, and the inherent compression achieved through procedural generation.