<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Programming Languages on Stuff by Aster</title>
    <link>https://stuffbyaster.org/blog/programming-languages/</link>
    <description>Recent content in Programming Languages on Stuff by Aster</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 13:21:22 -0400</lastBuildDate>
    <atom:link href="https://stuffbyaster.org/blog/programming-languages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Learning Parser Combinators: Part 1</title>
      <link>https://stuffbyaster.org/learning-parser-combinators-part-1/</link>
      <pubDate>Tue, 19 May 2026 13:21:22 -0400</pubDate>
      <guid>https://stuffbyaster.org/learning-parser-combinators-part-1/</guid>
      <description>&lt;p&gt;Today, I decided I would begin learning how to use parser combinators. Now I&amp;rsquo;ve been floating around&#xA;PLDev communities for quite a long time now, and everyone under the sun who enjoys declarative and&#xA;functional programming has told me to try parser combinators, that they would be one of the best&#xA;things that I have ever used in terms of extensible parsing. Now admittedly I have always kinda blown&#xA;this off, and that&amp;rsquo;s not to say I haven&amp;rsquo;t tried it before. When I attempted to learn these&#xA;combinators, I was told to start with &lt;a href=&#34;https://github.com/haskell/parsec&#34;&gt;Parsec&lt;/a&gt;, a very lovely&#xA;Haskell package, and it really is quite beautifully made.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
