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
- 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.
- 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?
- 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/#N4Igzg9grgTgx…
- 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:

