c
for c developers, code reviewers
Why this scored 5
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
medium confidence · estimate, not a guarantee7-day
~0
range 0–14
14-day
~0
range 0–17
30-day
~0
range 0–23
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.
- 142
Calculating 32-bit CRC for png
Validate png files · for c devs
stackoverflowSteady 2 · cdevtools53d ago - 238
Strange Corners of C
C language quirks discussed · for c devs
lobstersSteady 3 · cdevtools−6 saturated31d ago - 335
Implementing FMA and finding bugs in C and Rust standard libraries
Added fused-multiply-add support and uncovered bugs in C and Rust standard libraries. · for language library maintainers, systems programmers
lobstersSteady 3 · rustdevtools8d ago - 430
Into the void
New programming tools · for c devs
devtoSteady 2 · cdevtools34d ago - 527
InvisiCaps: The Fil-C Capability Model
New compiler capability model · for compiler devs
lobstersSteady 2 · cdevtools52d ago - 626
Rust's compile errors are other languages' production bugs
devtoSteady 3 · rust64d ago - 724
Memory Safety Absolutists
Memory safety discussion · for security engineers
lobstersSteady 3 · rustdevtools47d ago - 824
Rebuilding my C Redis clone in Rust taught me more Rust than any tutorial
devtoSteady 3 · rust66d ago - 923
Practical Memory Safety
Memory safety guide · for security engineers
lobstersSteady 5 · rustdevtools39d ago - 1023
Fil-C: Garbage In, Memory Safety Out
Memory safety solution · for c++ devs
lobstersSteady 3 · c++devtools49d ago - 1122
A quick overview of atomics in C
C atomic operations overview for safe concurrent programming. · for systems programmers
lobstersCooling 2 · cdevtools19h ago - 1222
kparser - small, readable parser for K
lobstersCooling 2 · c64d ago - 1321
PEP 814: Add frozendict built-in type
lobstersSteady 2 · c68d ago - 1421
Cron Jobs in C from Scratch
Cron jobs in C · for c devs
lobstersCooling 2 · cdevtools51d ago - 1519
Dependable C
Reliable c code · for c devs
lobstersSteady 2 · cdevtools53d ago - 1619
Is it okay to have a varied structure definition and implementation?
Varied struct definitions in C can affect code consistency and maintenance practices. · for c developers, code reviewers
stackoverflowSteadydevtools20h ago - 1719
Almost Always Unsigned (2022)
lobstersSteady 2 · c64d ago - 1818
an ambiguity in c89 which will never be fixed
c89 ambiguity · for c devs
lobstersSteadydevtools32d ago - 1917
How to call a statically linked Pascal function from a C main?
Shows how to link Pascal code statically and call it from a C program via FFI. · for systems programmers
stackoverflowSteadydevtools28d ago - 2017
the perils of parsing type inference declarations in c
C type inference issues · for c devs
lobstersSteady 2 · cdevtools48d ago