Repovex — GitHub repo scorecards for engineering teams (by jturner) — discussion

#devops #show

Why I Still Blog — and Why the Future of Blogging Is Connected (by sspaeti) — discussion

#editors #practices #vim #web

Pike - Solving the "should we stop here or gamble on the next exit" problem (via hoistbypetard) — discussion

#programming

Moonforge, A Yocto-Based Linux OS (via lemon) — discussion

#linux #release

A fully snapshotable Wasm interpreter (by matthewkim) — discussion

#programming #rust #wasm

Full-Source Binary Seed Bootstrap of the Guix System (via runxiyu) — discussion

#nix #security

Why should we have user age tracking in Operating Systems and websites? (by alcides) — discussion

#law #osdev

SQLite WAL-reset database corruption bug (via cve) — discussion

#databases

C++26 safety features won't safe you (via hunger) — discussion

#c++

Code reviews do find bugs (by kqr) — discussion

#practices

The State of Allocators in 2026 (via LesleyLai) — discussion

#plt #rust

U+237C is Azimuth (via chai) — discussion

#historical

The Emperor's Old Clothes: Tony Hoare's Turing Award Lecture (via orib) — discussion

#pdf #philosophy

Cellpond: Spatial programming without escape (via james) — discussion

#compsci #graphics #video #visualization

Type resolution redesign, with language changes to taste (via rcalixte) — discussion

#zig

Writing my own text editor, and daily-driving it (via Aks) — discussion

#editors

Pristan: The simplest way to create a plugin infrastructure in Python (by pomponchik) — discussion

#python #release

Embrace the uncertainty (via codekobold) — discussion

#practices #vibecoding

Unions merged into dotnet 11 preview 3 (via martinald) — discussion

#dotnet

Enamored with Macy (by addison) — discussion

#science