React 19 Breaks Async Composability

Ha great we finally arrive at the &quot;Next.js React features&quot; which basically forces everyone to use Next.js or an additional framework on top of React which now have to play catchup with whatever react - next.js think is &quot;best&quot; (for Vercels wallet). Expected outcome if half or the react core team is a Vercel employee.<p>Kinda new this day was coming, sad to see it actually happen

&gt; when navigating to a new screen, it&#x27;s better to show a loading state as soon as you can (often a skeleton UI), rather than delay the transition.<p>In a better language, this would be the programmers choice on a case-by-case basis, with no need for the higher-ups to break or fix everyone&#x27;s behaviour at once.<p>Either return a Page(Future(Components)) or a Future(Page(Components)).

I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.

Terrible shitshow. Web dev is all broken and horrible. Well at least the popular stuff is. No idea why anyone uses this outside resume building.

From the discussion:<p>&gt; My favorite way to do data fetching is as close to the place where I am using the data. React made it possible up until this change.<p>Well, yes, but we are nowadays in a situation where every component interacts directly with the state, or makes calls to the API (eg with the overuse of query), going against one of the architecture principles of react. It&#x27;s like we&#x27;re not building components, we&#x27;re building component sized micro-ui.

As a React dev at $DAYJOB, how React remains at the top despite the existence of infinitely better alternatives like Vue or Svelte will forever be baffling to me

I thought these two short video demos by Ryan Florence of how this problem is mitigated in the upcoming react router 7 would be relevant for this topic.<p>- <a href="https:&#x2F;&#x2F;x.com&#x2F;ryanflorence&#x2F;status&#x2F;1801383836250739057" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;ryanflorence&#x2F;status&#x2F;1801383836250739057</a><p>- <a href="https:&#x2F;&#x2F;x.com&#x2F;ryanflorence&#x2F;status&#x2F;1801388170891903252" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;ryanflorence&#x2F;status&#x2F;1801388170891903252</a>

What does that mean? (for someone not familiar with React)

is it something similar to Deferable Views in Angular? <a href="https:&#x2F;&#x2F;angular.dev&#x2F;guide&#x2F;defer#overview" rel="nofollow">https:&#x2F;&#x2F;angular.dev&#x2F;guide&#x2F;defer#overview</a>