<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>River on Ozbem</title><link>https://www.ozbem.com/tags/tech/river/</link><description>Recent content in River on Ozbem</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>info@ozbem.com (ebeem)</managingEditor><webMaster>info@ozbem.com (ebeem)</webMaster><copyright>© 2026 ebeem</copyright><lastBuildDate>Thu, 18 Apr 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.ozbem.com/tags/tech/river/index.xml" rel="self" type="application/rss+xml"/><item><title>River Protocol &amp; Architecture</title><link>https://www.ozbem.com/posts/tech/river/protocol/</link><pubDate>Thu, 18 Apr 2024 00:00:00 +0000</pubDate><author>info@ozbem.com (ebeem)</author><guid>https://www.ozbem.com/posts/tech/river/protocol/</guid><description>&lt;p&gt;
I’m currently studying &lt;code&gt;River&lt;/code&gt; in the hope of crafting a &lt;code&gt;guile&lt;/code&gt; scheme based window manager, &lt;code&gt;River&lt;/code&gt; uses a unique non-monolithic approach, unlike the &amp;#34;all-in-one&amp;#34; approach seen in many compositors, it splits the responsibilities of rendering and window management.&lt;/p&gt;
&lt;p&gt;
I am using this post as a living document to log my notes and findings as I study the &lt;code&gt;river-window-management-v1&lt;/code&gt; protocol. One done, it should be a great foundation for those who want to understand my window manager or write their own based on &lt;code&gt;River&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>