[yoe]

Hello, [yoe]

2026-05-02T00:00:00+00:00

After years of maintaining and shipping products with the Yoe Distribution</a>, we kept running into the same walls — most of them not technical, but cultural to the way embedded Linux has always been built. We started over, took the lessons that mattered, and wrote the tool we always wanted.</p>

What we kept</h2>

Machine abstraction and image composition.</strong> Yocto got a lot right here.</li>
Module composition.</strong> Pulling units from GitHub URLs scales to vendor BSPs.</li>
Tracking upstream closely.</strong> The cloud has been doing this for a decade.</li> </ul>
What we dropped</h2>

Cross-compilation as the default.</strong> Modern ARM and RISC-V boards build natively at full speed. Cloud CI runs arm64 cheaper than ever. QEMU user-mode emulation covers the rest.</li>
The SDK boundary.</strong> The same Go binary builds the kernel, the rootfs, and the application. No frozen sysroot, no drift, no “works on my SDK version.”</li>
Reinventing dependency resolution.</strong> Cargo, Go modules, pip, and npm already solved this. `[yoe]</code> composes with them instead of replacing them.</li>`
Generated shell scripts.</strong> When something fails, you should be reading the code you wrote — not a stack trace ten layers deep in machine output.</li> </ul> What we’re betting on</h2> AI as a first-class interface.</strong> Starlark units, queryable graphs, structured logs. An assistant that understands the system can take the cognitive load of “which knob, and why” off the developer.</li> One tool, three interfaces.</strong> AI conversation, interactive TUI, traditional CLI — same engine, same commands. Use whichever fits the moment.</li> Functional equivalence over bit-for-bit reproducibility.</strong> Hermetic builds and content-addressed input hashing without spending 20 years patching upstream.</li> </ul> [yoe]</code> is pre-1.0 and moving fast. Try it, break it, tell us where it broke.</p> — Cliff Brake</p>