<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jsr-354 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/jsr-354/</link>
    <description>Recent content in Jsr-354 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/jsr-354/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Moneta vs Joda-Money in 2026: Which Java Money Library Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-17-java-money-libraries-moneta-joda-money-jsr354-comparison/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-17-java-money-libraries-moneta-joda-money-jsr354-comparison/</guid>
      <description>&lt;p&gt;Every Java team eventually ships an invoice that is off by one cent. The cause is almost never a logic error — it is a &lt;code&gt;double&lt;/code&gt;. Money stored in a binary floating-point primitive accumulates error the moment you divide, and by the time a rounding step runs, the value has already drifted. The fix is not discipline; it is putting money behind a type that refuses to lose precision. In Java there are exactly two libraries worth considering for that job: &lt;strong&gt;JSR-354 / Moneta&lt;/strong&gt; and &lt;strong&gt;Joda-Money&lt;/strong&gt;. They make opposite architectural bets, and the wrong choice costs you either a heavyweight API you never use or a missing feature you have to build yourself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
