<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Client-State on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/client-state/</link><description>Recent content in Client-State on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 07 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/client-state/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 11: Server-State vs. Client-State: A Clear Distinction</title><link>https://ai-blog.noorshomelab.dev/tanstack-mastery-2026/11-state-separation/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/tanstack-mastery-2026/11-state-separation/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 11! In the world of modern web development, managing data is a central challenge. As applications grow in complexity, distinguishing between different types of data, and how we handle them, becomes critical for performance, maintainability, and user experience. This chapter dives deep into a fundamental concept: the difference between &lt;strong&gt;Server-State&lt;/strong&gt; and &lt;strong&gt;Client-State&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Understanding this distinction is not just academic; it&amp;rsquo;s a cornerstone for building robust applications, especially when leveraging powerful tools from the TanStack ecosystem like TanStack Query. We&amp;rsquo;ll explore why some data lives on your server, why other data lives purely in your browser&amp;rsquo;s memory, and how TanStack Query provides an elegant solution for the former, complementing your existing client-side state management.&lt;/p&gt;</description></item></channel></rss>