React v18.0
Congratulations to the React team on the release! I&#x27;ve kept up somewhat with the development of these features since Dan first introduced some of the ideas at JSConf 3 years ago. It&#x27;s interesting to see how the APIs have changed over time—I&#x27;m sure as a result of some tough lessons learned at Facebook.<p>As someone who has worked on large React projects worked on by multiple teams, I can see a lot of the value proposition being delivered in this release. I can already think of many places where I&#x27;ll want to slot in the transition API.<p>I&#x27;m curious if the SuspenseList API is making the cut here or if it&#x27;s still on the roadmap? I played with it a while back and thought it was very cool, albeit slightly niche perhaps.<p>The only part that&#x27;s a bit of a bummer is the recommendation on using suspense for data fetching. I&#x27;m already itching to get rid of lots of if (loading) {} code that plagues many of our components and makes orchestration and re-use of them a bit more painful than we&#x27;d like. I see lots of power in the idea of suspense as a way to orchestrate various generic async operations, but it feels like they don&#x27;t want us to build solutions on this abstraction unless we buy into some opinionated framework. I can&#x27;t really tell my team &quot;let&#x27;s use remix now lol&quot;.<p>All that being said this is a tremendous step forward and I&#x27;m looking forward to seeing what problems the React team tackles next.