Designing the compositor behind v3

When we started planning v3, the compositor was the obvious bottleneck. The old stack worked, but it left a lot of performance on the table — especially on integrated GPUs.

It's built on a tile-based renderer with explicit synchronization. Every window is a texture, every effect is a shader, and the scheduler aggressively skips frames that wouldn't change anything on screen.

The result: 240Hz on a fanless laptop, with battery life that's actually better than v2.