←
Joe Savona2,892 posts
Joe Savona avatar

Joe Savona

@en_JS

React team at Meta

◷ Joined April 2007▧ 13 Photos and videos
Joe Savona avatar
Joe Savona@en_JS·Mar 11

React Compiler: Rust edition is coming soon. We've ported the majority of the passes using AI. When the initial port finishes we'll do some updates to get the code in a state we're happy to maintain, then extensive testing and look at performance. More to come soon

Joe Savona avatar
Joe Savona@en_JS·Jan 30

Feels like subconsciously trying to retain control — "sure maybe i won't code but i'll retain control of the tasks". I think we have to let go of code and low-level tasks, direct the architecture and goals.

Joe Savona avatar
Joe Savona@en_JS·Jan 30

There are so many takes on the "give the agent a DAG of tasks" idea. But the reality is that task lists were always an attempt to impose order against fundamentally chaotic systems. You find the dependencies by doing tasks as often as you realize them in advance.

Joe Savona avatar
Joe Savona@en_JS·27 Oct 2025

For example it is probably not surprising that I disagree with many of the choices made by every React alternative (duh?). But instead of immediately dismissing those choices and learning nothing, I take some time to understand their goals and constraints.

Joe Savona avatar
Joe Savona@en_JS·27 Oct 2025

A thing that you can do, when seeing a technical choice you disagree with: pause. Take a breath. Be curious. Ask yourself, "why might they have done that?". Ask the authors why they did that? What context do they have that you don't?

Joe Savona avatar
Joe Savona@en_JS·25 Aug 2025

I'm really curious for feedback about React Compiler's error messages. Do people prefer very short ESLint-style messages ("can't do X") w no context/information, or informational messages with more information? Example: playground.react.dev/#N4Igzg…

Joe Savona avatar
Joe Savona@en_JS·27 Jun 2025

We've been pretty happy with TypeScript for React Compiler, but actual pattern matching (with exhaustiveness checking by default!) is so good it makes me want to port to Flow: flow.org/en/docs/match/

Joe Savona avatar
Joe Savona@en_JS·19 Jun 2025

For compiler nerds: a writeup of the core inference rules and approach that React Compiler uses to decide which groups of instructions to memoize together. If something isn't clear let me know! github.com/facebook/react/bl…

Joe Savona avatar
Joe Savona@en_JS·15 Feb 2025

The thing I loved about Create React App was that you could quickly install, hack on a single component, and quickly see changes. It was a great way to learn React. *All of the frameworks we recommend provide that exact experience*. Install, hack on the root component, iterate.

Joe Savona avatar
Joe Savona@en_JS·21 Jan 2025

Call me old fashioned, but I believe that people convicted of violently attacking police officers belong in jail.

Joe Savona avatar
Joe Savona@en_JS·14 Nov 2024

19rc1 is out with a new feature, sibling pre-rendering, that is the best of both behaviors. Amazing work by @acdlite and @sebmarkbage to implement this feature and @rickyfm, Jack Pope, and the rest of the team for verifying and rolling it out github.com/facebook/react/is…

Joe Savona@en_JS19 Jun 2024

Some thoughts on the suspense changes from 19 RC. Most important: our bad. We got this one wrong, and we heard and sincerely appreciate your feedback. We'll hold the 19 release until we find a good fix.

Joe Savona avatar
Joe Savona@en_JS·19 Jun 2024

So: we're working on changes to get feedback from y'all earlier. We're exploring a number of ideas including evolving our previous working groups and RFC process. We will definitely also re-evaluate canary to ensure that more developers can try out changes & new features earlier.

Joe Savona avatar
Joe Savona@en_JS·19 Jun 2024

We also don't want to privilege established players at the expense of making it hard for new libraries/frameworks/educators/voices to emerge. Rushing into a fix could backfire and lead us down the wrong path.

Joe Savona avatar
Joe Savona@en_JS·19 Jun 2024

This is harder than it seems (always is) because of the size of our community & many ways people use React. We need to balance info overload while getting a diverse, representative set of feedback.