Can It Run Doom? Yes, Even Your Relational Database

In the world of computer science, there is an unwritten, sacred law that has governed programmers for decades: if a device has a screen—or even a microprocessor remotely capable of doing math—someone must attempt to play the classic 1993 video game Doom on it.

Over the years, tech enthusiasts have gloriously forced the game to run on digital pregnancy tests, electronic toothbrushes, smart fridges, and printer display screens. But the latest triumph in hardware and software gymnastics doesn't involve strange gadgets at all. It happened inside one of the most famously un-fun places in tech: a relational database.

Asking Your Database to Fight Demons

If you aren't familiar with SQL, here is the short version: it stands for Structured Query Language, and it is the tool people use to ask databases plain questions. Usually, those questions sound like, "Can you find me every customer who bought socks in May?" or "Update this inventory count to twelve."

What SQL is not meant for is processing real-time graphics. It is built for data storage and retrieval, making it about as natural a choice for rendering a 3D video game environment as using a spreadsheet to paint the Mona Lisa.

Yet, driven by pure curiosity and magnificent over-engineering, a developer managed to craft a functional graphics renderer entirely out of database queries. Using roughly 1,300 lines of intricate SQL code, the system processes spatial calculations and generates bitmapped visual outputs of the game's iconic pixelated corridors.

35 Frames Per Second of Pure Overachieving

The most absurd part of this project isn't just that it works—it's how fast it runs. Database operations are notoriously heavy when pushed into strange mathematical corners. But this SQL renderer manages to churn out graphics at a targeted 35 frames per second.

To put that into perspective, 35 FPS was the smooth target frame rate of the original game when running on PC hardware back in the nineties. Achieving that kind of speed within a language designed to crunch spreadsheet-style rows and columns is nothing short of wizardry.

The Otterly Interesting Part

Why would anyone spend time forcing a database engine to do something it was clearly never intended to do? Because taking an everyday, pragmatic tool and stretching its rules until it performs magic is the highest form of digital play.

It is the modern equivalent of building a working grandfather clock entirely out of LEGO bricks. It reminds us that behind all our sleek apps and corporate spreadsheets, software engineering is still fundamentally a playground where clever minds test the boundaries of logic.

So the next time your company's database administrator tells you they are busy "optimizing queries," just know there is a non-zero chance they are actually admiring pixelated demon halls rendered right inside their command line. What unorthodox piece of technology should the tech world target next?

Keep exploring

• This Tiny Chihuahua Learned to Say 'I Love You' and We Are Not Okay
• California Brought Back Beavers After 70 Years—and the Little Guys Are Already Surfing
• The Covert CEO: How Rose Knox Secretly Built a Gelatin Empire
• Take an Otter quiz