<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Elixir on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/elixir/</link>
    <description>Recent content in Elixir on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/elixir/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Reactive Notebooks: Marimo vs Livebook vs JupyterLite</title>
      <link>https://www.pistack.xyz/posts/2026-06-09-self-hosted-reactive-notebooks-marimo-livebook-jupyterlite-guide/</link>
      <pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-09-self-hosted-reactive-notebooks-marimo-livebook-jupyterlite-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Notebooks have become the lingua franca of data science, exploratory programming, and technical documentation. But traditional notebooks like Jupyter suffer from a fundamental problem: hidden state. Cells execute in order, but the order you see on the page may not be the order they ran — leading to the infamous &amp;ldquo;works on my machine but not when I re-run from top&amp;rdquo; bug.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
