<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graalvm on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/graalvm/</link>
    <description>Recent content in Graalvm on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/graalvm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JRuby vs TruffleRuby vs MRI in 2026: Which Ruby Runtime Should You Actually Run?</title>
      <link>https://www.pistack.xyz/posts/2026-10-04-jruby-vs-truffleruby-vs-mri-ruby-runtimes-comparison/</link>
      <pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-04-jruby-vs-truffleruby-vs-mri-ruby-runtimes-comparison/</guid>
      <description>&lt;p&gt;Your Rails app is probably running on the same runtime it ran on five years ago, and that runtime is almost certainly MRI — the reference implementation. MRI is excellent, but it is not the only option, and for two very specific workloads it is not the fastest one either. Meanwhile the two alternative runtimes have both shipped major releases in the last month: &lt;strong&gt;JRuby 10.1.2.0&lt;/strong&gt; on 2026-09-21 and &lt;strong&gt;TruffleRuby 40.0.0&lt;/strong&gt; on 2026-09-17.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
