<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Time on Nalar</title>
    <link>https://nalar.dev/tags/time/</link>
    <description>Recent content in Time on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/time/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Monotonic Time Belongs in Elapsed-Time Measurement</title>
      <link>https://nalar.dev/monotonic-time-belongs-in-elapsed-time-measurement/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/monotonic-time-belongs-in-elapsed-time-measurement/</guid>
      <description>&lt;p&gt;A timeout can be represented by an ordinary timestamp comparison: record a start value, read the clock later, subtract, and compare the result with a limit. The arithmetic looks complete. The clock model is not.&lt;/p&gt;&#xA;&lt;p&gt;Civil time exists to place events on a shared calendar. It can be corrected to stay aligned with an external time reference. Elapsed-time measurement has a different requirement: later observations within one running system need an ordering suitable for measuring an interval. A clock correction that improves civil-time accuracy can therefore be harmful when the same reading is treated as a stopwatch.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
