futhark
for functional language developers, HPC engineers
Why this scored 1
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.
- 118
Keeping Futhark off the GPU
Choosing not to target GPUs influences performance expectations for Futhark users. · for functional language developers, HPC engineers
lobstersSteadyhardware23d ago - 216
How should Futhark expose irregular arrays to the programmer?
Futhark array exposure · for plt devs
lobstersSteadydevtools74d ago - 313
Rewriting the Futhark type checker
Futhark type checker rewritten · for plt devs
lobstersSteadydevtools96d ago - 413
Finally adding recursive functions to Futhark
Added recursive functions · for plt founders
lobstersSteadydevtools81d ago