<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Parsing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/parsing/</link>
    <description>Recent content in Parsing 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/parsing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DateTime Parsing Libraries: dateparser vs Chrono vs Joda-Time vs python-dateutil (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-self-hosted-datetime-parsing-libraries-dateparser-chrono-jodatime-dateutil/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-self-hosted-datetime-parsing-libraries-dateparser-chrono-jodatime-dateutil/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every self-hosted service that ingests data from external sources eventually confronts the datetime parsing problem. RSS feeds use RFC 2822. API responses use ISO 8601. Log files use whatever format the developer chose in 2008. User input arrives as &amp;ldquo;next Tuesday at 3pm&amp;rdquo; or &amp;ldquo;2026年6月20日&amp;rdquo;. A single misparsed date can cascade into missed alerts, duplicate billing cycles, or corrupted analytics. In a self-hosted data ingestion pipeline processing 100,000 documents per hour, even a 0.1% date parsing error rate means 100 corrupted records every hour.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Email MIME Parsing Libraries: mailparser vs MimeKit vs GMime vs Python email</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-email-mime-parsing-libraries-mailparser-mimekit-gmime/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-email-mime-parsing-libraries-mailparser-mimekit-gmime/</guid>
      <description>&lt;p&gt;Email communication remains the backbone of enterprise messaging, and behind every email client or server lies a critical component: the MIME (Multipurpose Internet Mail Extensions) parser. MIME parsers decode raw email bytes into structured objects — extracting attachments, handling character encodings, verifying signatures, and reconstructing messages from quoted-printable or base64 representations.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Parser Generator and Combinator Libraries: ANTLR vs tree-sitter vs nom vs pest vs nearley</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-parser-generator-combinator-libraries-antlr-treesitter-nom-pest-nearley/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-parser-generator-combinator-libraries-antlr-treesitter-nom-pest-nearley/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every programming language, configuration format, and domain-specific language (DSL) needs a parser. Whether you are building a compiler, writing a linter, or processing structured data, the parser is the component that transforms raw text into a structured abstract syntax tree (AST). Over the past three decades, the parsing tools ecosystem has evolved from monolithic parser generators to lightweight parser combinators and incremental parsing engines.&lt;/p&gt;</description>
    </item>
    <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>
