Give people something to link to so they can talk about your features and ideas (via twm) — discussion

#culture #practices

Summing ASCII encoded integers on Haswell at almost the speed of memcpy (via xoranth) — discussion

#c++ #performance

ASK: Should we have a "low content" or "low effort" flag? (by bomp)

#meta

Setting up a retro multi-node BBS on OS/2 Warp (via gmem) — discussion

#historical #video

I'm not a fan of strlcpy(3) (via markrages) — discussion

#c

Resurrecting a dead Dune RTS game (by wheybags) — discussion

#c++ #games #reversing #windows

Graphical effects in Duke Nukem 1 & 2, part 1 (via raymii) — discussion

#c #graphics

Why were early (personal) computer connectors so bulky? (via azeemba) — discussion

#hardware #historical

Shake Build System (via xiaq) — discussion

#haskell #practices

Using CSS nesting (via kaycebasques) — discussion

#web

EpicEpoch: A dialed-in hybrid timestamp service for scale (by danthegoodman1) — discussion

#distributed

New Old Stock OS/2 version 2 (via jmmv) — discussion

#historical

Privacy-Preserving Attribution (via thoroughburro) — discussion

#browsers #web

From the Lab to the Trading Floor: Designing for Expert Users (by yminsky) — discussion

#design #ml

Three important steps before jumping to the code (2022) (by stebunovd) — discussion

#practices

Exploring the challenges in creating an accessible sortable list (drag-and-drop) (via Sietsebb) — discussion

#a11y #design

AT&T: Unlawful Access of Customer Data (via tankf33der) — discussion

#release #security

wasm component as audio plugin (by chaosprint) — discussion

#audio #rust #wasm

Game Audio Programming Tutorial (via fcbsd) — discussion

#c++

Finding Simple Rewrite Rules for the PyPy JIT with Z3 (via tjf) — discussion

#compilers #python