bevy
for game devs, rust developers
Why this scored 18
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
Outlook
low confidence · estimate, not a guarantee7-day
~0
range 0–23
14-day
~0
range 0–29
30-day
~0
range 0–38
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
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.
- 139
It Breaks a Village: Bevy's 6th Birthday
Bevy's six-year milestone signals growing stability for the Rust game engine. · for game devs, rust developers
lobstersSteadydevtools1d ago - 237
Bevy's Sixth Birthday
Game engine birthday · for game devs
lobstersSteady 4 · rust31d ago - 335
Mapping voxel data to surface net vertices
voxel data mapping · for game devs
stackoverflowSteady 4 · rustdevtools28d ago - 416
Show HN: A self-running space economy SIM in Rust and Bevy
Rust space economy simulator · for game devs
hackernewsSteady 5 · rustother51d ago - 513
SIMD Vector Operations are slower than Normal Vector Operations when using `par_iter_mut`
SIMD vector operations · for rust devs
stackoverflowSteady 4 · rustdevtools52d ago