<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Json-Query on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/json-query/</link>
    <description>Recent content in Json-Query on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/json-query/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted JSON Processing CLI Tools: jq vs fx vs jid Comparison</title>
      <link>https://www.pistack.xyz/posts/2026-06-17-self-hosted-json-processing-cli-tools-jq-vs-fx-vs-jid/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-17-self-hosted-json-processing-cli-tools-jq-vs-fx-vs-jid/</guid>
      <description>&lt;h2 id=&#34;why-command-line-json-processors-matter&#34;&gt;Why Command-Line JSON Processors Matter&lt;/h2&gt;&#xA;&lt;p&gt;JSON is the lingua franca of modern APIs, configuration files, and data interchange. But working with raw JSON in the terminal — especially deeply nested structures from REST APIs — can be painful without the right tools. &lt;strong&gt;jq&lt;/strong&gt;, &lt;strong&gt;fx&lt;/strong&gt;, and &lt;strong&gt;jid&lt;/strong&gt; are three complementary approaches to terminal-based JSON exploration and transformation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
