<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chris Bannon</title>
    <description>The latest articles on DEV Community by Chris Bannon (@banzor).</description>
    <link>https://dev.to/banzor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F581123%2Fb5f4fd04-3666-431d-91d4-84dc8b38dbb2.jpeg</url>
      <title>DEV Community: Chris Bannon</title>
      <link>https://dev.to/banzor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/banzor"/>
    <language>en</language>
    <item>
      <title>React 18 startTransition Adoption</title>
      <dc:creator>Chris Bannon</dc:creator>
      <pubDate>Mon, 03 Oct 2022 14:23:24 +0000</pubDate>
      <link>https://dev.to/banzor/react-18-starttransition-adoption-4d2g</link>
      <guid>https://dev.to/banzor/react-18-starttransition-adoption-4d2g</guid>
      <description>&lt;p&gt;Hey, I have a simple question for the React community. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is your (or your team's) strategy on adopting the startTransion API?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The new concurrent rendering features are a breaking change, and opt-in. They bring new rendering benefits, but could cause rewrites/refactors in existing apps. It's always interesting to hear how others plan adopting of new APIs (especially those with breaking changes).&lt;/p&gt;

&lt;p&gt;So I'd like to hear from people, whether they are immediately adopting, waiting a little or postponing indefinitely the adoption of the new startTransition API.&lt;/p&gt;

&lt;p&gt;Any insight into your plans would be great to hear! Thanks&lt;/p&gt;

</description>
      <category>react</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
