Skip to content
Signalcrest
← Back to entity feed
devtoolsentity · corroborated across sources

common lisp

for lisp programmers

Cooling

7

signal score

as of 10d ago

1

live items

Too early

trajectory — needs a few more snapshots

lobsters

Why this scored 7

every term, weighted
Velocity+0.9 / 40 max

Its fastest-moving item, measured against the pace of its own source

Acceleration+0.0 / 25 max

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25 max

How many independent communities its own items come from

Recency+7.5 / 10 max

Decays to zero over 14 days, counted from when we first saw it

Saturation penalty1.4 / 30 max

Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it

Composite7.0

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)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

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.

  1. 116

    Why Target Common Lisp for Code Generation?

    Code generation with lisp — for devtools founders

    hackernewsdevtoolsSteady14d ago
  2. 28

    Common Lisp Portability Library Status

    Updates status of the Common Lisp Portability Library for cross-platform code. — for lisp programmers

    lobstersdevtoolsSteady6 saturated10d ago