seccomp — Unsafe at any speed (2022) (via LolPython) — discussion

#linux #security

Abusing .arpa, the TLD that isn’t supposed to host anything (via ysun) — discussion

#browsers #practices

Is legal the same as legitimate: AI reimplementation and the erosion of copyleft (by hongminhee) — discussion

#law #vibecoding

Removing recursion via explicit callstack simulation (by josephjnk) — discussion

#programming

Post-Quantum Cryptography Beyond TLS: Remain Quantum Safe (via fanf) — discussion

#cryptography

Notes on writing a voxel game in Dyalog APL (via juuso) — discussion

#apl #games #graphics

I don't know if my job will still exist in ten years (via lalitm) — discussion

#vibecoding

Your LLM Doesn't Write Correct Code. It Writes Plausible Code (via kitschysynq) — discussion

#vibecoding

Rust-like Error Handling in TypeScript (by csomar) — discussion

#javascript #programming #rust

Production query plans without production data (via sjamaan) — discussion

#databases #performance

Returning To Rails in 2026 (by mdr) — discussion

#programming #ruby #web

AI will fuck you up if you’re not on board (by rmoff) — discussion

#vibecoding

Open Sores (via animesh) — discussion

#culture

ASK: What are you doing this week? (by caius)

#ask #programming

Linux Internals: How /proc/self/mem writes to unwritable memory (via git-bruh) — discussion

#linux

Thinnings: Sublist Witnesses and de Bruijn Index Shift Clumping (by philzook) — discussion

#formalmethods #plt

Coding Agents Wrote a Chess Engine in Pure TeX (via azhenley) — discussion

#vibecoding

WebPKI and You (by bryce) — discussion

#security

Getting started with ClickHouse? 13 mistakes and how to avoid them (via knl) — discussion

#databases

Cambridge Battlecode: Code bots that compete in a turn-based strategy game (via azhenley) — discussion

#programming