Viewing profile — rickhanlonii

fwiw, the goal here wasn't to downplay the severity, but to explain the context to an audience who might not be familiar with CVEs and what's considered normal. I moved the note do…

Yeah agreed, thanks again for the feedback. The priority here is clear disclosure and upgrade steps.

GitHub has to review the advisories and publish it for it to show in `npm audit`, so it's delayed.

Thanks for the feedback, I adjusted it here so the first note is related to the impacted versions: https://github.com/reactjs/react.dev/pull/8195

After Log4Shell, additional CVEs were reported as well. It’s common for critical CVEs to uncover follow‑up vulnerabilities because researchers scrutinize adjacent code paths lookin…

That's a lot of questions, thanks for asking! I'll stick to answering the ones related to the new arch. The next thing is to continue building on this foundation and fix some long …

I don't know of any Flutter comparisons, but we shared some benchmarks here: https://github.com/reactwg/react-native-new-architecture/dis...

Will do, thanks paul big fan of your work

In the post we explain that this release removes the bridge, so the JS thread calls C++ directly without a queue, serialization, or bridge: https://reactnative.dev/blog/2024/10/23/…

Kind of. We already had a native UI tree running in native (the same way the browser has it's own internal representation of the DOM). The difference in this release is that we rew…

Yeah this is a tricky problem, and it's one of the reasons we updated our recommendation to use a framework like Expo that can make upgrades be smoother by being more opinionated a…

Capacitor is really cool because it allows you to build a web app in iOS and Android and access the platform APIs from JavaScript. The rendering layer is a bit different though, be…

I helped write this post, so feel free to ask me anything about the New Architecture!

Yeah we all know what you're talking about, you don't have to explain it. Testing is not the universally correct strategy for every case, and unless you take the time to understand…

From Jest's perspective, that amount is way over what we've needed to date.

We don't really need the funds and can't spent the ones we have, so we haven't pushed for more donations over the years.

Yeah, Meta will continue to use Jest internally. It still works really well for us, it's just "feature complete" for our use cases so we haven't needed to invest in it.

Meta is a backer of the Linux Foundation which OpenJS is a part of and has donated $22,000 to the Jest Open Collective which was created by Meta in 2016 to support non-employee Jes…

I started as a Jest core contributor before joining Meta. It's arguably the reason I work there now, and I'm really excited for the move. Meta created Jest and a lot of the feature…

We don't expect most users will interact with the `startTransition` API directly. Instead, it will be built into routing libraries and other infra code so you get the benefit of tr…

We plan to do this in a close follow up release! Automatic batching was one important step, because it starts to treat native events the same as events that goes through the synthe…