I no longer work on React! A few months back an opportunity came up to join a different team that I was excited about: I had been working around, then on, React for a combined 11+ years and was ready for a change, so I took the chance.

Wanted: a detailed specification format to ensure that AI doesn’t drift. Preferably with tooling that automatically checks if there are other areas of the codebase I need to consider as I work on the spec. Maybe realtime highlighting of any obvious mistakes I’m making in the spec document ;-)

The React Compiler rust port is now up as an in-progress PR at github.com/facebook/rea... - more to come as we test and polish.

[compiler] WIP port of React Compiler to Rust by josephsavona · Pull Request #36173 · facebook/react

This is an experimental, work-in-progress port of React Compiler to Rust. Key points: Work-in-progress - we are sharing early, prior to testing internally at Meta, to get feedback from partners in...

github.com

Joe Savona@en-js.bsky.social · 5mo ago

We’re pretty close to having an initial Rust port of React Compiler. My approach was to iterate on the plan document (write it manually, have the agent expand, edit, repeat). Then try to run it, see what goes wrong, revert back to the plan, tweak the plan, repeat.

“These are advanced features that can be skipped for now” Citation needed

We’re pretty close to having an initial Rust port of React Compiler. My approach was to iterate on the plan document (write it manually, have the agent expand, edit, repeat). Then try to run it, see what goes wrong, revert back to the plan, tweak the plan, repeat.

What if we all got together and agreed to pay a bit of money to the government every year so that they could put together a group of trained people to protect us from masked thugs in the streets?

Trend I’m seeing getting worse recently: a legit GitHub issue gets filed. Somehow people latch onto it as something they can spam us on. Multiple similar PRs, often from different people sharing bits of code, that look 90% plausible but with blatantly obvious tells.

Fuck yeah, this is the way. Diverse teams build better products. Good for Python.

Python Software Foundation@python.org · 9mo ago

as facilitating “the growth of a diverse and international community of Python programmers” is written directly into our mission and core to our values, so we withdrew our application.

A fun improvement to React Compiler, meant to be used in dev mode, that ensures anonymous functions get useful names. Instead of a blank name or “anonymous” in a trace you get eg “Card[<Header>.onClick]” or “useHook[variableName]”. github.com/facebook/rea...

[compiler] Option to infer names for anonymous functions by josephsavona · Pull Request #34410 · facebook/react

Adds a @enableNameAnonymousFunctions feature to infer helpful names for anonymous functions within components and hooks. The logic is inspired by a custom Next.js transform, flagged to us by @eps1l...

github.com

React folks: Id love your suggestions for an example app that stresses context update performance. I’m looking for something bigger than a micro benchmark, smaller than a full production app. Just complex to have a more realistic distribution of time in framework/product logic, ~1kloc

WIP writeup of the core inference rules that power React Compiler (coinciding w rewriting the guts of this algorithm to be more consistent, precise and powerful, especially for function expressions) github.com/facebook/rea...

I wish I’d had this when I was learning Japanese. domenic.me/fsrs/ So much wasted time reviewing cards unnecessarily, taking time away from learning new words. WaniKani is egregiously bad - I was (re)learning kanji very rapidly but soon hit a limit thanks to their terrible SRS algorithm and gave up