<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Repl on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/repl/</link>
    <description>Recent content in Repl on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/repl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Julia Toolchain in 2026: Juliaup vs Pkg.jl vs Revise.jl — Stop Restarting Your REPL</title>
      <link>https://www.pistack.xyz/posts/2026-09-13-julia-development-toolchain-juliaup-pkg-revise-comparison/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-13-julia-development-toolchain-juliaup-pkg-revise-comparison/</guid>
      <description>&lt;p&gt;Julia&amp;rsquo;s dirty secret is not performance — it is that most people evaluate the language with the worst possible toolchain. They install one version system-wide from a distribution package, edit code in one window, and then restart a REPL that takes forty seconds to re-load their packages. Every iteration costs a minute, so they conclude Julia is slow to work in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
