<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Beam on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/beam/</link>
    <description>Recent content in Beam on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/beam/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Elixir JSON Libraries: Jason vs Poison vs Jsonex vs Jsonrs</title>
      <link>https://www.pistack.xyz/posts/2026-07-25-elixir-json-libraries-jason-poison-jsex-jsonrs/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-25-elixir-json-libraries-jason-poison-jsex-jsonrs/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In the Elixir ecosystem, JSON parsing and encoding is one of the most common operations — from API responses to configuration files and message passing between services. While Erlang&amp;rsquo;s built-in string handling is powerful, Elixir&amp;rsquo;s functional programming paradigm demands libraries that are both fast and idiomatic. Choosing the right JSON library affects your entire application&amp;rsquo;s throughput, especially in high-traffic Phoenix web applications and real-time systems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
