<?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 Pi Stack</title>
    <link>https://www.pistack.xyz/tags/programming-languages/</link>
    <description>Recent content in Programming-Languages on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/programming-languages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Crystal Web Frameworks in 2026: Kemal vs Lucky vs Amber</title>
      <link>https://www.pistack.xyz/posts/2026-08-31-crystal-web-frameworks-kemal-lucky-amber-comparison/</link>
      <pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-31-crystal-web-frameworks-kemal-lucky-amber-comparison/</guid>
      <description>&lt;p&gt;Crystal compiles Ruby-like syntax into a single native binary that starts in milliseconds and handles tens of thousands of requests per second — no JVM warmup, no Node event loop, no Ruby VM. That performance story has been true for years, yet the language&amp;rsquo;s web framework ecosystem remains one of the best-kept secrets in backend development: three actively maintained frameworks — Kemal, Lucky, and Amber — each with more than 2,500 GitHub stars and commits pushed within the last month, and almost nobody writing about them. If you have ever wished Sinatra were compiled, Rails were type-safe, or Phoenix ran on a language that did not need the BEAM, one of these three is the framework you have been looking for.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
