<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MessagePack on Golden Hex</title>
    <link>/tags/messagepack/</link>
    <description>Recent content in MessagePack on Golden Hex</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 30 May 2026 13:30:00 +0000</lastBuildDate>
    <atom:link href="/tags/messagepack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Binary vs JSON for MCP: I Went Looking</title>
      <link>/2026/05/binary-vs-json-for-mcp-i-went-looking/</link>
      <pubDate>Sat, 30 May 2026 13:30:00 +0000</pubDate>
      <guid>/2026/05/binary-vs-json-for-mcp-i-went-looking/</guid>
      <description>&lt;p&gt;Protobuf beats JSON on CPU and memory. Apache TinkerPop&amp;rsquo;s GraphBinary, same story over GraphSON - I&amp;rsquo;m living that migration at work, and we&amp;rsquo;re already seeing memory pressure ease. The tradeoff is old: text is readable but costs CPU and bytes, and past a certain payload size that cost outweighs the convenience.&lt;/p&gt;&#xA;&lt;p&gt;I wanted to go looking for that. My first thought was the Language Server Protocol - but LSP is a decade old: settled, widely shipped, and with little appetite for changing the bytes on its wire.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
