Go 1.26 interactive tour (via makishimu) — discussion

#go

A field guide to sandboxes for AI (by beowolx) — discussion

#ai #devops #virtualization

Uncloud, self hosted Cloud, seen by a developer for developers (by athoune) — discussion

#devops #networking

Who Owns the Memory? Part 3: How Big Is your Type? (by lukefleed) — discussion

#c #c++ #rust

Kelp: A New Streaming Log Parser Algorithm (by trueleo) — discussion

#compsci #rust

Detect Go’s silent arithmetic bugs with go-panikint (via olegkovalov) — discussion

#go

How Github monopoly is destroying the open source ecosystem (via toastal) — discussion

#culture #vcs

komorebi Financial Breakdown for 2025 (by jeezy) — discussion

#finance #law

Functors, Applicatives, and Monads: The Scary Words You Already Understand (via nemin) — discussion

#elm #plt

Compiler Engineering In Practice - Part 2: Why is a compiler? (via dhruvp) — discussion

#compilers

It’s hard to justify Tahoe icons (via ehamberg) — discussion

#design #ios #mac

Rate limiting bursty workloads (via schonfinkel) — discussion

#databases

Sneaking Metadata into Mako Templates (by rbr) — discussion

#python

journal-guardian: JournalCTL Watcher with local LLM explanations for errors (by delirehberi) — discussion

#devops #linux

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

#ask #programming

Using eBPF to load-balance traffic across UDP sockets with Go (via fanf) — discussion

#linux #networking

Databases in 2025: A Year in Review (via fanf) — discussion

#databases

A Practical guide to building a parser in Go (via mysticmode) — discussion

#compilers #go

Decorative Cryptography (via Foxboron) — discussion

#cryptography #linux #security

FreeBSD Home NAS, part 5: ZFS pools, datasets, snapshots, and monitoring ZFS health (by setevoy) — discussion

#freebsd #unix