All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

River 0.4.0 Introduces Non-Monolithic Wayland Architecture Separating Compositor and Window Manager

By

dpassens

2mo ago· 10 min readenInsight

Summary

The article discusses a significant architectural shift in Wayland compositors, focusing on river 0.4.0's non-monolithic approach that separates the window manager from the compositor. This breaks from traditional monolithic architectures where both components are combined into a single program. The new river-window-management-v1 protocol allows window managers to control window positioning and management independently, enabling greater flexibility and compatibility with existing window managers.

Key quotes

· 3 pulled
Traditional Wayland compositors have a monolithic architecture that combines the compositor and window manager into a single program.
The new 0.4.0 release of river, a non-monolithic Wayland compositor, breaks from this traditional architecture and splits the window manager into a separate program.
The stable river-window-management-v1 protocol gives window managers full control over window positioning.
Snippet from the RSS feed
Traditional Wayland compositors have a monolithic architecture that combines the compositor and window manager into a single program. This has the downside of requiring Wayland window managers to do the significant work of implementing an entire Wayland c

You might also wanna read