Temper Language (via veqq) — discussion

#plt

Too many words about DIDs (via icy) — discussion

#distributed #web

How my images are dithered (via abnercoimbre) — discussion

#graphics

Kommit-ing to a icon (via FedericoSchonborn) — discussion

#art

openQA Testing in KDE Linux (via FedericoSchonborn) — discussion

#linux #testing

Tensor is the might (via eatonphil) — discussion

#ai #c

Beautiful Type Erasure with C++26 Reflection (via lcapaldo) — discussion

#c++

Is x86 ready to ACE it? (via hoistbypetard) — discussion

#hardware

Hating AI in 2026 (via mtset) — discussion

#practices #vibecoding

6× faster binary search: from compiled code to mechanical sympathy (by itamarst) — discussion

#performance #rust

Jurassic Park computers in excruciating detail (via jbauer) — discussion

#historical

git-absorb: git commit --fixup, but automatic (via krig) — discussion

#vcs

Job queues are deceptively tricky (by typesanitizer) — discussion

#distributed #practices

CSS-DOS — A computer made of CSS (via outervale) — discussion

#css #vibecoding #web

Collection of clock designs (via wherewhy) — discussion

#design

The git history command deserves more attention (via gnyeki) — discussion

#vcs

From coder to curator (via nolan) — discussion

#vibecoding

fred: A text editor that uses C for everything - Handmade Network Expo 2026 (via linkdd) — discussion

#c #programming #video

ASK: Should Libraries Log or Propagate Errors? (by veqq)

#ask #programming

Estimating the heights of New Yorkers from their scuff marks (by veggie) — discussion

#visualization