<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Stateless Operating System</title>
        <link>https://diode.zone/videos/watch/05f5537e-ffe1-4769-a3ff-ebcc21ab9868</link>
        <description>With Guix and Nix it's possible to treat OS as a value of the function depending solely on specified inputs (packages+configurations), but some parts during runtime still produce, store and modify different values. How to be sure that you aware of all such cases? How to reduce mutable state of Operating System and make it as explicit as possible? Let's dig in. 0:00 Introduction 1:16 Problems of undesired state 5:30 Is Stateless OS possible? What problems? 7:33 Immutable OS is a first part of solution 10:20 Ideal workflow 12:05 Completing the first solution 14:40 Second part of the solution: User state 17:05 Realistic workflow 18:16 Making sure that all state is under control 20:46 Possible state types 26:45 Conclusion Notes: https://gist.github.com/abcdw/343ce43004c8a435c5ac603ba081f307 rde repository: https://github.com/abcdw/rde</description>
        <lastBuildDate>Tue, 20 Oct 2026 14:41:14 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://diode.zone</generator>
        <image>
            <title>Stateless Operating System</title>
            <url>https://diode.zone/lazy-static/avatars/61b689b7-84d5-43c7-9fa8-e63a7fd1d952.png</url>
            <link>https://diode.zone/videos/watch/05f5537e-ffe1-4769-a3ff-ebcc21ab9868</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://diode.zone/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://diode.zone/feeds/video-comments.xml?videoId=05f5537e-ffe1-4769-a3ff-ebcc21ab9868" rel="self" type="application/rss+xml"/>
    </channel>
</rss>