<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Abseil on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/abseil/</link>
    <description>Recent content in Abseil on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 25 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/abseil/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C&#43;&#43; String Manipulation Libraries: Abseil Strings vs Folly FBString vs StringZilla for High-Performance Servers</title>
      <link>https://www.pistack.xyz/posts/2026-06-25-cpp-string-libraries-abseil-folly-stringzilla/</link>
      <pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-25-cpp-string-libraries-abseil-folly-stringzilla/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;String processing is one of the most common operations in server software — parsing HTTP headers, serializing JSON, building SQL queries, or formatting log messages. Yet the standard &lt;code&gt;std::string&lt;/code&gt; in C++ carries performance characteristics that become bottlenecks at scale. Every copy, every small-string allocation, and every substring operation triggers heap interaction. This article compares three production-grade C++ string manipulation libraries: &lt;strong&gt;Abseil Strings&lt;/strong&gt;, &lt;strong&gt;Folly FBString&lt;/strong&gt;, and &lt;strong&gt;StringZilla&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
