doom
for backend engineers, database developers
Why this scored 0
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 130
We ported the original Doom to SQL
Porting classic Doom to SQL shows database engines can run game logic. · for database engineers, game devs
lobstersSteady 2 · doomother21d ago - 221
DOOM running on a regex engine
doom on regex · for game devs
lobstersEmergingother91d ago - 318
It's always Doom https://ood.dev/posts/doom/
The post examines Doom's code and design, highlighting lessons for modern game development. · for game developers
devtoSteadyother73d ago - 417
We ported the original Doom to SQL
Porting Doom to SQL illustrates SQL's Turing-completeness for unconventional programming. · for backend engineers, database developers
hackernewsSteadydevtools21d ago - 517
DOOM, Emacs
Emacs and Doom mentioned · for emacs users
lobstersSteadydevtools86d ago - 66
Running Doom on Our Custom CPU and Going Viral
Custom CPU runs Doom · for hardware engineers
hackernewsSteadyhardware97d ago