rickhanlonii

5 ms·

1.
by rickhanlonii 9mo ago
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 down so the more important information like severity
2.
by rickhanlonii 9mo ago
Yeah agreed, thanks again for the feedback. The priority here is clear disclosure and upgrade steps.
3.
by rickhanlonii 9mo ago
GitHub has to review the advisories and publish it for it to show in `npm audit`, so it's delayed.
4.
by rickhanlonii 9mo ago
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
5.
by rickhanlonii 9mo ago
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 looking for variant exploit techniques to test whether the initial
6.
by rickhanlonii 2y ago
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 standing issues things like scroll perf and text i
7.
by rickhanlonii 2y ago
I don't know of any Flutter comparisons, but we shared some benchmarks here: https://github.com/reactwg/react-native-new-architecture/dis...
8.
by rickhanlonii 2y ago
Will do, thanks paul big fan of your work
9.
by rickhanlonii 2y ago
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/the-new-architecture...
10.
by rickhanlonii 2y ago
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 rewrote it in C++ and made it immutable. That means instea
11.
by rickhanlonii 2y ago
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 about the setup. As the core library, we need to support
12.
by rickhanlonii 2y ago
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, because in React Native you can use the platform APIs _and_ th
13.
by rickhanlonii 2y ago
I helped write this post, so feel free to ask me anything about the New Architecture!
14.
React Native: The New Architecture Is Here(twitter.com)
2 points by rickhanlonii 2y ago|0 comments
15.
by rickhanlonii 3y ago
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 their use case, you're really not in a posit
16.
by rickhanlonii 4y ago
From Jest's perspective, that amount is way over what we've needed to date.
17.
by rickhanlonii 4y ago
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.
18.
by rickhanlonii 4y ago
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.
19.
by rickhanlonii 4y ago
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 Jest contributors. Jest actually has all the funds we need righ
20.
by rickhanlonii 4y ago
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 features that it's known for, but it's true tha
21.
Concurrent React(youtube.com)
1 points by rickhanlonii 4y ago|0 comments
22.
by rickhanlonii 4y ago
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 transitions without need to wrap all the state updates yo
23.
by rickhanlonii 4y ago
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 synthetic event system. The rest will be a bigger breaking change
24.
by rickhanlonii 6y ago
"Widely documented" means that it's trivial for you to look up the data yourself.
25.
Jest 24: Refreshing, Polished, TypeScript-Friendly(jestjs.io)
1 points by rickhanlonii 8y ago|0 comments
26.
by rickhanlonii 9y ago
They're listening, but not to your voice or with a microphone. Facebook is listening to your data--to all of our data, all at once. They have locations, searches, clicks, messaging, photos, hashtags, and any other form of browsing patt
27.
by rickhanlonii 9y ago
Could be shared IP or even just "target people located near people who are targets" since they have location data
28.
by rickhanlonii 9y ago
I can think of a few problems with this just off the top of my head: The first x minutes of a post are _heavily_ influential in the success of the post, editing after allows you to hijack successful titles for gain (spam) For large subs, po
29.
by rickhanlonii 9y ago
Great rant about something way over my head by someone who knows way more than me about it! If I can transfer to a domain I understand better (front-end dev): It sounds like VMs, Jails, and Zones are like Ember.js: it comes with everything
30.
by rickhanlonii 10y ago
There are certainly other reasons. For example, I only comment as an admission of failure to express my self in code. Most of the time a better variable name or adding a function with a descriptive name will say the same thing as a comment

More ›