Letter from Codeberg: Onwards and upwards (via FedericoSchonborn) — discussion

#vcs

Reverse Engineering the Miele Diagnostic Interface (via fanf) — discussion

#hardware #reversing

Web playground for training language models with WebGPU (by vin) — discussion

#ai #rust #show #wasm #web

OSS Friday Update (by noteflakes) — discussion

#ruby

Helping Valve to Power Up Steam Devices (via bkardell) — discussion

#games #graphics #linux #performance

impala - A TUI for managing wifi on Linux (by pythops) — discussion

#linux #rust

Think you can’t interpose static binaries with LD_PRELOAD? Think again (via gioele) — discussion

#programming

Nix Sucks; Everything else is Worse: Building Better Software Supply Chains (via Zamicol) — discussion

#cryptography #nix #vcs #video

Understanding QCOW2 Risks with QEMU cache=none in Proxmox (via abi) — discussion

#virtualization

web pentaculum - a satanic webring hosted on OpenBSD.amsterdam (via drkhsh) — discussion

#openbsd

Building a Minimal Viable Armv7 Emulator from Scratch (via mpweiher) — discussion

#assembly

Source code for a 1977 version of Zork (via snej) — discussion

#games #lisp

Go's runtime may someday start explicitly freeing some internal memory (via runxiyu) — discussion

#go

We should all be using dependency cooldowns (by yossarian) — discussion

#security

There's always going to be a way to not code error handling (via EvanHahn) — discussion

#plt #rust

More tales about outages and numeric limits (via puida) — discussion

#devops

Undo, Redo, and the Command Pattern (by Johz) — discussion

#practices #programming

How/Why to Sweep Async Tasks Under a Postgres Table (via cve) — discussion

#databases #practices

FAWK: LLMs can write a language interpreter (by janiczek) — discussion

#plt #vibecoding

Why (pure) functional programming matters (by chreke) — discussion

#education #video