<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>State-Management on Štěpán's web and blog</title><link>https://granat.blog/tags/state-management/</link><description>Recent content in State-Management on Štěpán's web and blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://granat.blog/tags/state-management/index.xml" rel="self" type="application/rss+xml"/><item><title>React doesn't need a state management tool, I said. Then I built one.</title><link>https://granat.blog/posts/2026-07-24-react-arven/</link><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><guid>https://granat.blog/posts/2026-07-24-react-arven/</guid><description>&lt;p&gt;A while back I wrote an article with a title I stand behind to this day: &lt;a href="https://dev.to/tolgee_i18n/react-doesnt-need-state-management-tool-i-said-31l4"&gt;React doesn&amp;rsquo;t need a state management tool&lt;/a&gt;. There&amp;rsquo;s already a library for everything, and each new one just adds another decision to an exhausting pile.&lt;/p&gt;
&lt;p&gt;So naturally, the next thing I did was build a React library. Before you close the tab — give me a chance. I think I have a decent excuse, and it doesn&amp;rsquo;t actually contradict a word of that article.&lt;/p&gt;</description></item></channel></rss>