There is an interesting thread on the Go issue tracker about daemonizing processes. Most of the thread is not about daemonizing processes though, but more about why Go has no Fork() function which you can call directly in your code. The first time I read through it I was wondering and saying to myself: “Yeah, why is there no Fork()? It surely can’t be that hard to implement.” After all you can already call system calls with the syscall package. As I read more and more I realized that the problem is not implementing Fork() per se, but rather implementing Fork() to work safely in a multi-threaded environment, which most Go programs are. So I tried to find out why.
Forking is Cool, or: A Unix Shell in Zig, or: Dave Learns How to Fork - ratfactor
In this article, I make a real, working interactive shell written in Zig. Though essentially a toy, it demonstrates the incredible elegance of the fork() system call and is an example of what can be done with absolutely no runtime memory allocations.
Learn Go by Building a Command Line Todo App | Barbarian Meets Coding
Learn the Go programming language by building a test-driven command line todo application
No Fork Required - Scott's Thoughts
What if another operating system isn't the solution to anything at all? What if device-level identity could tie into existing systems to help pull users out of walled gardens, rather than creating new gardens?
Mastodon creator shares what went wrong with Threads and ponders the future of the fediverse
In a wide-ranging interview with Eugen Rochko, creator of the decentralized social network Mastodon, Rochko shared why Threads federation fell flat, why ActivityPub and ATProto will likely never merge, and what it will take to grow the fediverse.
Dancing mad with sandboxing
Kefka is a Go-native shell sandbox with coreutils, Python via WebAssembly, and more. Learn the works of madness that went into making this happen!
Vibe-coded Go static analysis tools
Ideas are now a major bottleneck for vibe-coding. There are whole categories of software that simply don’t occur to me to write. Philip Zeyliger pointed me at one: Go static analysis tools. These are great candidates: easy to describe easy to test high value low risk He created a checker that requires slog.InfoContext instead of slog.Info when a context is available, to improve our telemetry/observability. I followed up with a checker that lets you annotate a Go struct as requiring complete, explicit annotation.
Why the Fuss About Serverless? | HackerNoon
To explain this, I’m going to have to recap on some old work with a particular focus on co-evolution.
Crossing the Hyper-Thread Boundary - exe.dev blog
Your VMs can share a CPU core. You get to decide who they share it with.
Evaluations Are the Real Codebase - The Phoenix Architecture
Why behavior outlives implementations
Don't couple your Go code to GitHub | Iain Cambridge
The technical musings of Iain Cambridge.
Extensible Software in the age of LLMs | Jeremy Morrell
Solid core + capability-based sandboxes + LLMs = Users with superpowers
Lexidraw, an Excalidraw fork where your drawings follow you
Lexidraw is an Excalidraw fork where your drawings follow you. Share publicly with the Atmosphere or privately with iroh.
Stigmergy
Stigmergy is a mechanism of indirect coordination, through the environment, between agents or actions. The principle is that the trace left in the environment by an individual action stimulates the performance of a succeeding action by the same or different agent. Agents that respond to traces in the environment receive positive fitness benefits, reinforcing the likelihood of these behaviors becoming fixed within a population over time.
the world hasn’t figured out yet that you can literally just fix everything with a Nix overlay
There are many things that are uncertain in our industry right now, but one thing I am certain about, and have been for almost 13 years, is that Nix is a terrible programming language. I remember when I first learned it, it felt like pushing shit uphill. The learning cliff
