Guides
Constraint, readability, and the two-second loop. Three design reasons a 1993 platformer can still outplay a 2026 release.
Play a well-regarded 16-bit platformer tonight and then play a modern one. The older game usually responds faster, explains less, and respects your time more. That is not nostalgia; it is a set of design constraints that vanished.
The first constraint was memory. A cartridge had room for a handful of sprites, so every enemy had to be readable at a glance. Modern games can render a hundred enemies, and often do, which makes silhouette design optional and visual noise inevitable.
The second was the two-second loop. With no save states and no tutorials, a game had to teach through level design. The first screen taught jumping, the second taught timing, the third combined them. That pedagogy is still the best onboarding model anyone has produced.
The third was input latency. A controller wired to a console responded in a few milliseconds, and games were tuned around that. Modern engines add a frame or two of buffering, and while nobody notices in a cinematic game, everyone notices in a platformer.
None of this argues that old games are better. It argues that constraints produce clarity, and that clarity is a feature you can choose to design for. The best modern retro games are not imitations; they are games that kept the constraints on purpose.
If you want to test the thesis, pick a retro platformer you have never played. Do not read a guide. Give it twenty minutes and count how many times it explains something without words.