iiinova — where your digital self keeps evolving

Reposted by Ricky

dan @danabra.mov · 25/06/2026

... i have joined the @nextjs.org team at @vercel.com. for a start, i'll be working part-time, so please don’t flood me with bug reports yet. however, i’ll try to keep an eye on them as i want to understand what problems Next.js users are running into every day. i want App Router to get good!

3131723

Ricky @ricky.fm · 25/06/2026

It's sooooo nice when people don't just post feedback but actually submit PRs. Max is great, be like Max.

2303

Reposted by Ricky

Max @maxwellcohen.bsky.social · 24/06/2026

The awesome newly updated `use()` docs show more ways to make `use()` a truly useful API, for data loading on the client and the server. Thank you to @ricky.fm and @aurorascharff.no for writing, and @brenelz.com, @stephanjnoel.bsky.social , and @yadiel.dev for reviewing! react.dev/reference/re...

react.dev

use – React

The library for web and native user interfaces

1296

Reposted by Ricky

Max @maxwellcohen.bsky.social · 09/06/2026

🚨🚨🚨 React Compiler Rust Port is merged!!! Thank you to Mofei, Mike, @ricky.fm, @en-js.bsky.social, and @no.lol for their work on the port! github.com/react/react/...

screenshot showing react compiler port to rust is merged

1344

Reposted by Ricky

Joe Savona @en-js.bsky.social · 11/03/2026

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.

49812

Reposted by Ricky

Max @maxwellcohen.bsky.social · 16/02/2026

useActionState is a new hook for forms, async reducers, and more. It now has great new documentation: react.dev/reference/re... Thank you to @ricky.fm for writing. Thank you to @aurorascharff.no, @danabra.mov, @samselikoff.com, @stephanjnoel.bsky.social, @brenelz.com, and @yadiel.dev for reviewing.

react.dev

useActionState – React

The library for web and native user interfaces

0175

Ricky @ricky.fm · 10/02/2026

Does this diagram help? It uses the React Performance Tracks to explain what React is doing, and what you'll see when you use the tracks: github.com/reactjs/reac...

3303

Ricky @ricky.fm · 08/02/2026

Adding more information to React error pages github.com/reactjs/reac...

0381

Reposted by Ricky

Max @maxwellcohen.bsky.social · 06/02/2026

useEffectEvent makes handling events in Effects much easier and saves unnecessary unmounting and remounting of listeners. It now has awesome new docs: react.dev/reference/re... Thank you to @ricky.fm the updates, and @danabra.mov and @stephanjnoel.bsky.social for reviewing

react.dev

useEffectEvent – React

The library for web and native user interfaces

1416

Reposted by Ricky

Johan Nohr @nohr.se · 01/02/2026

Take me down to the Parallax city where the far moves slow and the near moves quickly

93166274819

Ricky @ricky.fm · 28/01/2026

The future came, and it's not annoying

270

Reposted by Ricky

Colum Kelly @columk.bsky.social · 16/01/2026

www.columkelly.com/blog/use-opt... Updated the todo examples and some of the writing after getting feedback from @ricky.fm To be fair, Ricky's version of the final example is very clean, (although it took me a while to grasp). useOptimistic might save you after all.

columkelly.com

useOptimistic Won't Save You | Colum Kelly

Thoughts on the useOptimistic hook that was introduced in React 19

182

Ricky @ricky.fm · 17/01/2026

My Async React talk from React Conf is up! www.youtube.com/watch?v=B_2E...

youtube.com

Async React

YouTube video by React Conf

1422

Ricky @ricky.fm · 15/01/2026

codesandbox.io/p/sandbox/co...

2210

Ricky @ricky.fm · 11/12/2025

Please update (again) immediately.

27014

Reposted by Ricky

React @react.dev · 11/12/2025

Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.

217669

Ricky @ricky.fm · 23/11/2025

I’ve programmed since I was 11 and got a minor in CS, but I wanted to be a math teacher. I was offered a 35k math teacher position replacing a retiring teacher making 70k, and was told “this is how it works you have to take it”. I said no, two weeks later I started at a software engineer for 70k.

3470

Reposted by Ricky

slate @pleasebegneiss.bsky.social · 21/11/2025

any historian able to tell me what stage of democracy it is in when the leader is saying “off with their heads”

1442693557

Reposted by Ricky

Aurora Scharff @aurorascharff.no · 17/11/2025

Going back through @ricky.fm's Async React as I prep an internal talk, and this part is insanely good, felt like it deserved a reshare🔥 youtu.be/p9OcztRyDl0?...

0347

Reposted by Ricky

Ryan Carniato @ryansolid.bsky.social · 06/11/2025

People give `useEffect` a bad rap, but it isn't usually the source of the problem. The real problem is too many `useState`s. Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/

7697

Reposted by Ricky

Seb ⚛️ ThisWeekInReact.com @sebastienlorber.com · 05/11/2025

The React core team when they see devs using useEffect

114520

Reposted by Ricky

dan @danabra.mov · 29/10/2025

aargh someone kill me. literally THE WHOLE POINT of directives is that they’re not just strings! they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST. and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls

This event also led to various discussions in the community, following the introduction of parametrized directives (’use cache: private’ / ’use cache: remote’), and the introduction of a Vercel ’use workflow’ directive the next day. Many developers argue it’s dangerous to use strings and would prefer function decorators or explicit typesafe API calls. We still need to think about it before making up our minds and taking a side, but here are some related links worth checking out:

11866

Ricky @ricky.fm · 26/10/2025

Anyone remember asm.js? It allowed you to add "use asm" directives to functions and runtimes would compile them to binary. It was ahead of its time, but was criticized as forking JavaScript syntax and creating vendor lock in for Firefox. It became WebAssembly.

4572

Ricky @ricky.fm · 26/10/2025

This is very cool! For React devs, the closest analog is the new Activity API. There are pros/cons of each - for example with Activity you kinda have to do some ceremony to pre-render on hover, and this fork() API makes that a bit easier, but I think Activity covers more use cases.

3440

Ricky @ricky.fm · 15/10/2025

please stop dm’ing me that it’s just backbone.js all over again

1302

Reposted by Ricky

dan @danabra.mov · 11/10/2025

i think the @react.dev Compiler team could include more of this type of messaging. i'm being a bit inflammatory here (and Haskell may not the best analogy), but the principle of "pure things are safe to move around" is fundamentally simple and has been known for decades. teach it to new generation!

You may not like it, but React is basically Haskell.

The React Compiler works for the same exact reason that compilers for pure programming languages are able to make non-trivial optimizations.

If your code is composed of pure functions, it is safe to re-order their computation, or save the result for some inputs and reuse it for later for same inputs. This is not some kind of a “workaround” or a hack — it’s one of the most exciting consequences of the functional programming paradigm which has been known and used for decades.

Purity and idempotency make it safe to move stuff around without changing the final outcome. Following the "rules of React" is just ensuring your code is safe to move around like this.

1023122

Ricky @ricky.fm · 11/10/2025

I might do a deep dive later on. I didn’t go into the sync example much, but if you do, you find yourself having to use a bunch of refs and effects just to get a semi good experience. There are no refs or effects with async react features.

1290

Reposted by Ricky

dan @danabra.mov · 09/10/2025

i thought @ricky.fm talk was very good. i hope they’ll glue it up together from two days into a cohesive video. slightly sad about the last example breaking (a one-line mistake) but such is the nature of live demos. overall i think it’s a great conclusion to last ten years of work from the team. 💜

2775

Ricky @ricky.fm · 08/10/2025

Part 2 is on the schedule, I’m just going to start the demo over and finish the talk from there

3401

Reposted by Ricky

zeu @zeu.dev · 08/10/2025

react <Activity> be like

0583

Ricky @ricky.fm · 08/10/2025

Part 2 will be at React Conf tomorrow

2400

Ricky @ricky.fm · 07/10/2025

My talk is just suspended, I’ll finish it later

6801

Ricky @ricky.fm · 03/10/2025

This explains why useEffectEvent took so long to ship. We tried a lot of alternatives, but they all hit this problem. We decided to ship it with all the constraints, because it’s useful even when constrained, but I’m still hoping for a general solution.

1260

Ricky @ricky.fm · 02/10/2025

This is React Fiber:

3594

Reposted by Ricky

Seb ⚛️ ThisWeekInReact.com @sebastienlorber.com · 01/10/2025

<Activity> - The most exciting React feature just came out! Hide a React subtree and unmount its Effects while preserving its state, and keep rendering it with lower priority. Unlocks very exciting pre-rendering patterns along the way! More Activity modes are coming

2606

Ricky @ricky.fm · 01/10/2025

Anyone remember React Fiber?

3270

Reposted by Ricky

dan @danabra.mov · 28/09/2025

banger

# But doesn’t that lead to confusion?

It certainly seems to lead to confusion on Twitter.

3283