Separating the Wayland Compositor and Window Manager

Wayland just dropped a twist worthy of reality TV: the non‑monolithic compositor river 0.4.0 splits the “window boss” from the “graphics engine,” so you can mix‑and‑match the way your windows behave while river does the smooth visuals and plumbing. Translation: custom layouts without the usual Wayland glue traps, thanks to a new protocol that hands window managers full say over positions and shortcuts while keeping performance tight.

The crowd? Spicy. One camp is celebrating like it’s a season finale: asveikau calls plug‑in window managers on Wayland “doing god’s work,” cheering a future where swapping your window rules is as easy as changing a theme. Another camp rolled up in leather jackets with a 90s attitude: wild_egg wonders “why Wayland is even a thing,” swearing X11—the old display system—still bends to every whim. Then there’s mikkupikku, threatening to run X11 “forever,” joking they’ll recruit coding agents to keep it breathing.

Amid the fireworks, a practical flex: oofbaroomf says they built a “vibe‑coded” personal river window manager that finally tiles exactly how they want—something they couldn’t wrangle in other setups. Meanwhile, the nitpick patrol arrived: jauntywundrkind quibbled over diagrams and who talks to the kernel, reminding everyone that nothing in Linux land ships without a debate.

Verdict from the peanut gallery: river’s split could bring X11‑style freedom to Wayland without the lag. But the culture war—comfortably custom X11 vs. clean‑slate Wayland—rages on.