feat: 0.76 Release Blog Post #4279
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
blakef
force-pushed
the
0.76-release-blog
branch
5 times, most recently
from
55ccb5c to
381e25c
Compare
blakef
force-pushed
the
0.76-release-blog
branch
3 times, most recently
from
b118484 to
1ff6856
Compare
There was a problem hiding this comment.
Great job with the blogpost! 👏 👏 👏 👏 👏
I left some suggestions to streamline it a little bit more. Also, we need to run the linter on it! @blakef
There was a problem hiding this comment.
Things that could be worth it to include:
- Swift template? (although it's in a separate repo now) react-native-community/template#45
- Metro 0.81 (and mention recent perf gains)? https://github.com/facebook/metro/releases/tag/v0.81.0
- Not sure it's worth mentioning, but CSS isolate: facebook/react-native#45883
- Modal backdropColor? facebook/react-native#46322
This will not land in 0.76. The 0.76 branch of the template still has the objective-c code, so it will not pop up in the upgrade helper and any new project in 0.76 with the template will still have the code in objective-c. That's why we omitted it.
This is worth calling out, especially because we also call that out at React Universe on the stage. cc. @blakef
This feels like a detail of the views that was introduced to make other properties that depends on the stacking context work better.. Do you think that many people might want to use this prop?
This feels like something too small to make it to the blogpost. When we write the blogpost, we try to put there the highlights that might attract the most people or the announcement we want to make. A specific prop in a specific component is something that only person that is really interested into should look for in the Changelog or in the documentation. |
|
Thanks Forgot that Oskar said Swift template was for 0.77 I understand and doubt many will use CSS |
|
@blakef can we fix the PR? it fails to lint, build and deploy. |
Retain only mid/low blast radius breaking changes.
Typos and missing changes
blakef
force-pushed
the
0.76-release-blog
branch
from
44e29e0 to
b534854
Compare
|
|
||
| In the old architecture, React Native communicated with the native platform using an asynchronous bridge. To render a component or call a native function, React Native needed to serialize and enqueue native functions calls with the bridge, which would be processed asynchronously. The benefit of this architecture is that the main thread was never blocked for rendering updates or handling native module function calls, since all work was done on a background thread. | ||
|
|
||
| However, users expect immediate feedback to interactions to feel like a native app. This means some updates need to render synchronously in response to user input, potentially interrupting any in-progress render. Since the old architecture was only asynchronous, we needed to rewrite it to allow for both asynchronous and synchronous updates. |
There was a problem hiding this comment.
Follow-up on my previous comment: I still feel that rendering synchronously is still potentially confusing, since that may be interpreted as rendering synchronously from the main thread
There was a problem hiding this comment.
After reading the 2 final blog posts, added a few improvement suggestions:
- Is RN 0.76 the first RN version upgrading to React 18? 🤔
- The with/without transition demo is a bit confusing
- Remove react-tweet lib?
Also, what about adding an announcement bar "The New Architecture is here" to replace this one?
Otherwise, both are great blog posts! 🥳
| "react": "^18.2.0", | ||
| "react-dom": "^18.2.0", | ||
| "react-github-btn": "^1.4.0", | ||
| "react-tweet": "3.2.1", |
There was a problem hiding this comment.
Is this lib imported anywhere? looks like you embed the Metro tweet as an iframe in the end
|
|
||
| ## How to Upgrade | ||
|
|
||
| To upgrade to 0.76, follow the steps in the [release post](/blog/2024/10/23/release-0.76-new-architecture#upgrade-to-076). Since this release also upgrades to React 18, you will also need to follow the [React 18 Upgrade guide](https://react.dev/blog/2022/03/08/react-18-upgrade-guide). |
There was a problem hiding this comment.
Isn't RN using React 18 for a while already?
The release blog post. This is an early draft that requires community feedback on:
Please avoid bike-shedding where possible.