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

TFTP Honey pot Results (via mtlynch) — discussion

#security

Adding a second middleware broke our typescript types (by Linell) — discussion

#javascript #programming

ASK: lobste.rs is now running on SQLite (by thomas0)

#meta

A Farewell to ARPs: IPv4 Service on IPv6-Only Networks (via fanf) — discussion

#networking

FreeBSoD: Leveraging Language Models to Find and Exploit Kernel Bugs (Part 1 of 2) (via fro) — discussion

#freebsd #security #vibecoding

FreeBSoD: Leveraging Language Models to Find and Exploit Kernel Bugs (Part 2 of 2) (via fro) — discussion

#freebsd #security #vibecoding

Go-flavored concurrency in C (via telemachus) — discussion

#c #go

Human Emacs (via tusharhero) — discussion

#emacs