Awesome! Glad this is finally out, and really looking forward to seeing what features the React team adds in follow-up releases.<p>The Working Group model really helped us in the community give feedback - APIs like `useSyncExternalStore` wouldn't have happened otherwise, and I really appreciate the responsiveness on that topic.<p>FWIW, React-Redux v8 is in beta right now:<p>- <a href="https://github.com/reduxjs/react-redux/releases" rel="nofollow">https://github.com/reduxjs/react-redux/releases</a><p>I think it's basically ready to go, but I haven't had a chance to really test out the SSR support I added a couple months ago. I'd love to have some help testing that out.<p>v7 will _run_ with React 18, but v8 has been specifically reworked to behave correctly when used with React's new "Concurrent Rendering" capabilities. We've also converted React-Redux itself to TS (no more separate types package).<p>Ideally, I'd like to release v8 as final in the next week or two.
I wish React removed all the compatibility code it has with Internet Explorer and the likes and worked on minimising the weight. Also the synthetic events reactivity system seems a bit outdated.<p><a href="https://www.solidjs.com" rel="nofollow">https://www.solidjs.com</a> is quite awesome but lacks the React ecosystem.
React is not only introducing layers and layers of abstractions/ concepts that are hard to grasp for a newcomer, they are also reclaiming well-established terms.<p>> A transition is a new concept in React to distinguish between urgent and non-urgent updates.<p>> Urgent updates reflect direct interaction, like typing, clicking, pressing, and so on.
> Transition updates transition the UI from one view to another.
Fun fact: I started building a couple React apps 5 years ago. Apps still run, but since they're class based component and don't use hooks, the apps feel like ancient. They run perfectly fine though. New guys don't really want to work on in though. Hooray for progress.
We've also posted a tweet thread breaking down the main features, so please check it out if you enjoy that format! <a href="https://twitter.com/reactjs/status/1508838714180612100" rel="nofollow">https://twitter.com/reactjs/status/1508838714180612100</a>
Congratulations to the React team on the release! I've kept up somewhat with the development of these features since Dan first introduced some of the ideas at JSConf 3 years ago. It's interesting to see how the APIs have changed over time—I'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'll want to slot in the transition API.<p>I'm curious if the SuspenseList API is making the cut here or if it'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's a bit of a bummer is the recommendation on using suspense for data fetching. I'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'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't want us to build solutions on this abstraction unless we buy into some opinionated framework. I can't really tell my team "let's use remix now lol".<p>All that being said this is a tremendous step forward and I'm looking forward to seeing what problems the React team tackles next.
I wonder how concurrent mode in React stacks up with Solid.js. It seems React has been adding more and more features + complexity, while other frameworks are re-thinking the approach from the ground up building a simpler and faster primitive, yet keeping the same jsx primitives.
We've heard rumblings that react18 implies the need for major changes in legacy projects. For instance, jest testing suites apparently need to move away from enzyme?<p>Also, is there something about MUI and react18 that makes styled-components more of a pain? Not sure where I heard that.
Congratulations to the React team! I remember three years ago when Dan first showcased some of the concurrent features [1], so this has been quite long in the making.<p>[1] <a href="https://www.youtube.com/watch?v=nLF0n9SACd4" rel="nofollow">https://www.youtube.com/watch?v=nLF0n9SACd4</a>
Amazing news…congrats to the React team!<p>We have been running the RC in prod since January and it’s been super smooth<p>Concurrent mode makes react apps much, much faster and snappier…huge win for perf!
Exciting to see so much server-side focus in all recent development. IMO React has massive value outside of the usual static site or SPA making API calls use cases. Eagerly waiting for Server Components to get ready.
When is the Suspense documentation going to be updated? I don't see it in the beta docs, and the main documentation page is for v17, so its still marked as experimental. It also says that, "Before React 18 is released, we will replace this page with stable documentation."
I was really hoping that they would have internal implementation by now to automatically infer the missing dependencies array for hooks so we need not rely on an external linting tool. This is one of the most common issues faced by react devs.
Really excited about the transitions (edit: I mean batching) for state updates. I always found it so frustrating that updating 3 different state values in a callback would cause 3 separate renders.
If you have a list of elements rendered in a container (from array), does React always re-render the whole thing (contents of container) when adding / removing elements from the array or is there a way to work around that? I'm coming from Svelte, I would not be learning React if it was not for its omni-presence in the job market and I'm genuinely curious.
@danabramov would you mind sharing the rationale behind making the ReactWG invite only? I understand that, de jure, it's Facebook's property, and you all can do whatever you want with it. De facto, since so many people on the outside world contributed to the project, at least an election of a commission would have been warranted. Would you mind commenting?
The Transitions look nice but I feel like this will bloat code incredibly. Maybe it‘s meant only as an optimisation to be used sparingly but if I would always have to also start a transition when I do some conditional rendering it will generate a lot of overhead code. Or am I wrong?
I wonder how it will compare to v17 on the JS benchmarks.<p><a href="https://krausest.github.io/js-framework-benchmark/current.html" rel="nofollow">https://krausest.github.io/js-framework-benchmark/current.ht...</a>
Yet again, another React major version, more churn in the ecosystem. Are all of the libraries your app depends on compatible with the new version? How much effort to update the ones that aren't, if that's even possible? Get ready to spend tens of your team's man-hours answering these questions.
Starting from the introduction of hooks all react updates have been going backward.<p>The biggest benefit of react for me always been it's brutal conceptual simplicity. It's been a reliable tool and now it turned into the monster.
"The most important addition in React 18 is something we hope you never have to think about: concurrency." - really? this is what our technical prowess has come to?
Congratulations, but
to me React is like Rust. Something I always wanted to get into but found better alternatives.
In the react case Vue wins for me and in the Rust case it's Go.<p>I really tried, time and time again to like it and write something with it, but Vue just offers the better libraries. Altough with the recent 2 to 3 upgrade and pinia instead of vuex I'm starting to get dissatisfied with the "no single proper way" of Vue. Vuex-orm being the best frontend REST wired ORM, nothing comes close to ease of use and setup.
Meanwhile react has what? Complicated redux, or is that even a thing anymore? Idk, which I would. Redux the boilerplate abomination. That's exactly what drove me away from Angular.
But I'm starting to rant again.
And react has even more of the "not a single proper way". Yeah I know, nextjs the magic bullet, but what if you don't agree with pretty much everything about it, starting with routing.