<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sonic on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sonic/</link>
    <description>Recent content in Sonic on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sonic/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go JSON Libraries: encoding/json vs jsoniter vs easyjson vs gojay vs Sonic</title>
      <link>https://www.pistack.xyz/posts/2026-07-05-go-json-libraries-encoding-jsoniter-easyjson-gojay-sonic/</link>
      <pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-05-go-json-libraries-encoding-jsoniter-easyjson-gojay-sonic/</guid>
      <description>&lt;p&gt;JSON serialization is a critical path in virtually every Go web service. The standard library&amp;rsquo;s &lt;code&gt;encoding/json&lt;/code&gt; is correct and well-maintained but prioritizes simplicity over raw performance. For latency-sensitive APIs, data pipelines, and high-throughput services, specialized JSON libraries can deliver 2-10x speedups. This article compares five Go JSON libraries — &lt;strong&gt;encoding/json&lt;/strong&gt;, &lt;strong&gt;jsoniter&lt;/strong&gt;, &lt;strong&gt;easyjson&lt;/strong&gt;, &lt;strong&gt;gojay&lt;/strong&gt;, and &lt;strong&gt;Sonic&lt;/strong&gt; — across performance, API compatibility, and tradeoffs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
