<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Units-of-Measurement on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/units-of-measurement/</link>
    <description>Recent content in Units-of-Measurement on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/units-of-measurement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Units of Measurement in 2026: JSR-385 (Indriya) vs Unit-API vs JScience</title>
      <link>https://www.pistack.xyz/posts/2026-09-18-java-units-of-measurement-jsr385-indriya-unit-api-jscience-guide/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-18-java-units-of-measurement-jsr385-indriya-unit-api-jscience-guide/</guid>
      <description>&lt;p&gt;A satellite lands in the wrong orbit because one team wrote pound-force and another read newtons. A billing system charges a customer 1,000x too much because a duration was stored in milliseconds and compared against seconds. A chemical dosing API returns 10 mg instead of 10 µg. These are not exotic failures — they are the default outcome of passing bare &lt;code&gt;double&lt;/code&gt; values between layers and hoping that everyone agrees on the unit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
