<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Response Time on Nalar</title>
    <link>https://nalar.dev/tags/response-time/</link>
    <description>Recent content in Response Time on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/response-time/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Fast Motion Can Leave Trails on a Screen</title>
      <link>https://nalar.dev/why-fast-motion-can-leave-trails-on-a-screen/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/why-fast-motion-can-leave-trails-on-a-screen/</guid>
      <description>&lt;p&gt;A screen can have a high refresh rate and still show a faint trail behind a moving cursor, dark text, or a fast object in a game. This effect is often called &lt;strong&gt;ghosting&lt;/strong&gt; or &lt;strong&gt;smearing&lt;/strong&gt;. It can make motion look less clear even when the animation itself is running smoothly.&lt;/p&gt;&#xA;&lt;p&gt;The key idea is that refreshing the screen and changing each pixel are related but different jobs. A display may receive a new image on time while some pixels are still moving toward the brightness or colour that the new image requires.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
