<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Xml on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/xml/</link>
    <description>Recent content in Xml 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/xml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted XML Parsing Libraries: lxml vs pugixml vs Xerces-C&#43;&#43; vs rapidxml (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-self-hosted-xml-parsing-libraries-lxml-pugixml-xerces-rapidxml/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-self-hosted-xml-parsing-libraries-lxml-pugixml-xerces-rapidxml/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Despite JSON&amp;rsquo;s dominance in modern APIs, XML remains the backbone of countless enterprise systems, configuration formats, document standards, and legacy integrations. SOAP web services, SAML authentication, RSS/Atom feeds, SVG graphics, XHTML documents, and Android layout files all rely on XML parsing. For self-hosted services that ingest or transform XML data — whether you&amp;rsquo;re building a document conversion pipeline, an RSS aggregator, or a SOAP gateway — your choice of XML parsing library directly impacts throughput, memory usage, and correctness.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
