<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>String-Formatting on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/string-formatting/</link>
    <description>Recent content in String-Formatting on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/string-formatting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted String Formatting Libraries: fmtlib vs ICU vs Abseil Strings vs boost::format (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-self-hosted-string-formatting-libraries-fmtlib-icu-abseil-boost-format/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-self-hosted-string-formatting-libraries-fmtlib-icu-abseil-boost-format/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;String formatting might seem mundane, but in large-scale self-hosted services it directly impacts CPU utilization, memory allocation patterns, and localization capabilities. A logging pipeline processing 500,000 lines per second spends 15-30% of its CPU time on string formatting. An API gateway that constructs JSON error messages from templates allocates millions of temporary strings per hour. Choosing the right formatting library can reduce your service&amp;rsquo;s CPU usage by 40% compared to naive &lt;code&gt;sprintf&lt;/code&gt; or &lt;code&gt;std::stringstream&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
