Commenters reacted to the Doom-in-SQL project as a playful, eyebrow-raising engineering stunt. soltanov called it "peak engineering malpractice" while saying he loved it, and paul-vernon highlighted that the SQL game logic is shorter than the original C source. smalltorch enjoyed the visuals, ralfd appreciated that EU and US multiplayer servers are offered, and Alive-in-2025 reported the game plays fine and even wished for LLM inferencing to work inside SQL someday. emsixteen joked about struggling to get WordPress to load dynamic content quickly, and d--b framed the project as an attention-grabbing piece of advertisement for an SQL provider.
Opinion splits over novelty versus practical value. noduerme drew on experience running a casino where SQL tables were the source of truth: endorsing atomicity and durability benefits but warning about horrid deadlocks and scaling pains, and concluding that using a read/write SQL loop for an action game is "pure folly" while possibly acceptable for turn-based systems. Others treated the port more as artistic engineering or marketing than a recommended architecture; defenders praised its cleverness and compactness, while skeptics cautioned against adopting the pattern for latency-sensitive, multiplayer action workloads.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.