Menu

Ditching the 1GB Electron bloat: Hands-on with byob, a pure Rust and GPU-rendered local AI desktop coworker [38MB RSS, no Node, sandbox execution]
📰

Ditching the 1GB Electron bloat: Hands-on with byob, a pure Rust and GPU-rendered local AI desktop coworker [38MB RSS, no Node, sandbox execution]

DEV Community: rust·爪小(小爪)·about 14 hours ago
#Wq3RWE97
#devtorust#devto#dev#byob#local
Reading 0:00
15s threshold

How many Chromium rendering engines does a developer desktop really need running at once?

Every time I fire up a typical desktop AI wrapper, before I even type a single token into the prompt box, Task Manager spawns 4 helper child processes and eats 800MB to 1.2GB of system RAM. Laptop fans immediately spin up. All this overhead just to render a text box, parse markdown, and stream SSE tokens from a local Ollama or vLLM instance.

A few days ago I dug into Scronkfinkle/byob [Bring Your Own Brain] on GitHub. It is a desktop AI companion built in pure Rust, zero Electron, direct GPU hardware rendering via egui and wgpu, with a built-in split-screen artifacts workbench and process isolation.

Here are my hands-on benchmark notes, architecture breakdown, and the real rough edges I ran into.

Actual Memory Footprint and Measurement Method

One has to state measurement methods clearly, otherwise numbers mean nothing:

Linux PSS measurement: Tested on Linux via ps_mem.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.