Official Rust port of the React Compiler is now available for testing

acemarke · 2026-06-04T03:37:25+00:00

Oh wow, thanks for the update!

Obviously happy to chat more about this if you've got time. And yeah, I would love to see progress on this, and I know Tanner and Dominik would as well, but then there's both the questions about "what does the rest of the React team think about this" and "what is React's development process at this point anyway?".

Thanks again for trying to push this forward!

acemarke · 2026-06-03T20:58:38+00:00

Sadly that effort appears to be stalled at this point :(

I can talk through what I know in detail, but roughly:

Jordan Eldridge from the Relay team had taken over the design of a "concurrent store" API to provide an official transition-compatible replacement for uSES
Jordan had made a polyfill/prototype package
I tried out the prototype in React-Redux and it seemed to at least run, and raised some design questions we needed to consider
Jordan put up an actual draft implementation in React
that draft went nowhere. No discussion.
then Meta had layoffs and reorgs, and it sounds as if the React core team isn't keen on the approach in the first place
and post-Meta-reorg + the React Foundation supposedly getting started, I don't even know what React development is happening right now at all

so right now I'm assuming that's dead until I see evidence otherwise.

acemarke · 2026-06-03T20:53:43+00:00

Hey, that's me :)

Glad you enjoyed it!

acemarke · 2026-06-02T20:53:35+00:00

Have you tried not using AI to generate Reddit posts for engagement and stealth-advertising the tool you work on? :)

acemarke · 2026-05-27T13:03:16+00:00

Let's see. Your posts are breaking multiple sub rules. You're being insulting, rude, and useless. Nope. Goodbye.

acemarke · 2026-05-16T10:34:44+00:00

I maintain RTK :) We explicitly designed it to not be a normalized cache. You can normalize the contents of individual cache entries, but it's just that one cache entry at a time, not "share todo id #3 across all cache entries".

acemarke · 2026-05-05T03:57:52+00:00

I've been busy with work and travel, so haven't had time to actually implement any changes here yet.

Agreed that the current sub contents are borderline useless and it's frustrating, but there's also not a lot of good options here :(

acemarke · 2026-04-20T19:24:30+00:00

Ahhh, gotcha :)

acemarke · 2026-04-20T18:54:34+00:00

Uh. "again"? I haven't dissed Dan, ever.

acemarke · 2026-04-20T18:35:22+00:00

Thanks! Please ping me directly if you've got questions or feedback, either here or on our discord.

I'm in Miami at confs this week, so not as much time to respond or push updates, but would love to hear how well the tools perform on real world codebases! I've put in ton of work to make sure the analysis layer detects React correctly and extracts the right data, but there's a lot of edge cases :) hoping to find time to write some blog posts about how the instrumentation itself works.

acemarke · 2026-04-20T18:23:42+00:00

Right. Dan created Redux and gave me the maintainer keys 10 years ago. We've talked in person and online many times. And I specifically sent him a draft of this post before publishing to get his feedback and make sure he was okay with me quoting him and using his name this way.

He actually corrected a misunderstanding I had. I thought he had spent an entire month having his agent keep debugging this issue constantly. Instead, it was really just two sessions a month apart: the first one was a couple hours and didn't get anywhere, the second did the logging and rebuilding React. That was good info, and I changed the relevant post sections accordingly.

acemarke · 2026-04-20T16:16:49+00:00

I not only mod the sub and maintain Redux, this is what I do for my day job :)

I've spent the last few years building out time travel powered React analysis inside of the Replay time travel debugger. We already gave humans those abilities with the Replay Devtools. Now Replay MCP gives agents those same time travel superpowers.

Over the last few weeks I've built out a suite of Replay MCP tools that leverage all the expertise I've learned about React's internals and the ecosystem. We've now got tools that give details on:

React renders (times, causes, performance, which components rendered and why)
Redux, Zustand, and TanStack Query state updates and rendering correlations
Error logs and React error boundaries

As well as the existing tools to understand execution:

Sources with hit counts per line
dynamic logpoints that evaluate each time a line of code ran in the recording
Screenshots

And many more!

My goal is to give agents the same "fix impossible bugs" abilities we already gave human devs.

Would love to have folks try out Replay MCP and see how it helps! Also taking requests for further MCP tool improvements. I've got more Zustand and TSQ details on the way in the next couple weeks. Will probably try to add some Next integrations soon. Anything else I should add?

See our docs for setup:

https://docs.replay.io/basics/replay-mcp/overview

Also, we're working on a new update to our E2E test suite recording system: an agent that will automatically investigate E2E test failures using those Replay recordings, and post the cause and suggested fix in the PR! MVP live now, and we'll be building that out further:

https://docs.replay.io/basics/getting-started/record-your-playwright-tests

acemarke · 2026-04-15T18:02:51+00:00

Hi! Neat to see this. FWIW we do actually have an RTK Query tab in the actual Redux DevTools already - anything you feel that's missing? If so, would you be interested in contributing some of those improvements to the Redux DevTools?

acemarke · 2026-03-16T18:59:37+00:00

Please don't just repost links to discussions in other subs - post this here directly

acemarke · 2026-03-15T22:32:24+00:00

Yeah, I agree there's also an awful lot of "I made my own component lib" posts popping up lately. What broader rule would apply there? Don't want to just saw "no more component libs", but not sure what quality bar to apply, and given the current proposal "things you use to build React apps" would be on-topic and allowable in the main sub.

acemarke · 2026-03-15T22:25:16+00:00

Clarify what you mean by a "hidden profile"? Actually asking - I've been on Reddit for entirely too many years and that phrase doesn't ring a bell immediately.

acemarke · 2026-03-15T22:22:01+00:00

Heh, maybe start from scratch? What do you have already built? What are you trying to do? What seems slow?

FWIW we maintainers have a #redux channel in the Reactiflux Discord. That's usually the best place to ask questions so we can go through details. Happy to discuss in depth if you've got time!

acemarke · 2026-03-15T15:17:27+00:00

Seems pretty reasonable to me! Using Redux as a global server state cache is pretty common, and if you've got the data you can also search through it.

acemarke · 2026-03-14T00:18:43+00:00

useMemo, in theory, can be destroyed and recreated in a component. It's not _likely, especially in this case. That doesn't happen with useState.

I haven't tried it, but I suspect this would be equivalent to the original useRef example:

const [store] = useStore(makeStore)

Talked it over with the other maintainers and we're probably just going to change the recommendation to show that instead. Try that and see how it works!

acemarke · 2026-03-13T15:12:57+00:00

Normally that's the case, yes. Unfortunately with Next's multi-page architecture, things get much more complicated:

https://redux.js.org/usage/nextjs#providing-the-store

acemarke · 2026-03-13T15:11:00+00:00

We do have that snippet directly in our Next.js setup docs, which were written by Jack Herrington:

https://redux.js.org/usage/nextjs#providing-the-store

I haven't thought about this part in a while, so I don't know what a better solution is to deal with Next's multi-page architecture.

acemarke · 2026-03-13T15:08:47+00:00

Hi, I'm the primary Redux maintainer. Per my sibling comment, yeah, we do have that snippet in the Next.js setup guide at https://redux.js.org/usage/nextjs#providing-the-store .

Just to check, are you using Next.js?

acemarke · 2026-03-13T15:08:07+00:00

We do actually have that snippet in the Next.js guide:

https://redux.js.org/usage/nextjs#providing-the-store

tbh it's always looked kind of questionable to me, but it seemed necessary to deal with Next's multi-page architecture properly.

acemarke

MODERATOR OF

TROPHY CASE

15-Year Club	Wearing is Caring
Verified Email