Crossing the Hyper-Thread Boundary - exe.dev blog

Extensible Software in the age of LLMs | Jeremy Morrell

Solid core + capability-based sandboxes + LLMs = Users with superpowers

co/core — an AI cooperative

co/core is a cooperative for AI inference — people pooling the Macs they already own to run open models for each other, instead of renting from the big clouds. An experiment in AI infrastructure we build, share, and own together. Bring your existing OpenAI-compatible code, or share a Mac and help run it.

co/core · 5.0 ★ | at-store

co/core is a cooperative for AI inference — people pooling the Macs they already own to run open models for each other. Tag: Developer.

The Virtual OS Museum

Over 1,700 pre-installed operating systems spanning 1948 to today, in a single Linux VM. Bundled QEMU, VirtualBox, and UTM. One-click launchers for Windows and Linux.

Can we billionaire-proof inference? - Graze Newsletter

A small, federated compute co-op called co/core — and the wider experiment it's a part of.

Coasts — Containerized Hosts for AI Agents

Free, open source parallel runtimes for AI agents. Run multiple isolated environments on your machine — no cloud, no conflicts.

Welcome to the Strix Halo Wiki!

Welcome to the Strix Halo Wiki! The purpose of this website it to gather important information and practical guides for systems powered by AMD Ryzen AI MAX and MAX+ processors. Our guides cover various topics and of course there is a separate section…

Tangled CI runs on microVMs

How we built spindle's new QEMU-based microVM engine

What Even Is An OS Now?

Computers now work the way I thought they did when I was 8. What does computing look like when most applications have an audience of 1-2 people? I'm leaving Fly.io to build a phone for that world.

Sprites - Stateful sandboxes

Persistent, hardware-isolated execution environments for arbitrary code. Run AI agents, untrusted code, and more in secure sandbox environments with checkpoint & restore.

Thorsten Ball - Why threads can't fork

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.

Why Futhark?

A high-performance and high-level purely functional data-parallel array programming language that can execute on the GPU and CPU.

I've gone full Nix: Proxmox to NixOS + Incus | Bas Nijholt

After years of running a Proxmox cluster, I migrated my entire homelab to NixOS with Incus. I explain the philosophical friction of imperative 'appliance' OSs vs declarative hosts, share how I migrated my LXC/VM workloads, and why it is the perfect infrastructure to manage using AI agents.

Setting up a virtual machine with GPU passthrough

A guide for configuring NixOS with nvidia GPU passthrough to a virtual machine in virt-manager.