I'm not sure explanations for these terms really belong on react.dev. I've actually been thinking about starting a dedicated site that explains all of these concepts in one place, so frameworks and libraries can simply reference it. I even picked up a domain for it 😂

Hand them a messy codebase, a bug, a feature request, and an AI agent.

The real signal is how they explore, iterate, and collaborate with the tools that actually ship product.

Angular really nailed releases: a major every 6 months + codemods

Maybe there could be a collapsible “Deep Dive” section labeled something like “Coming from classic React?” with a short summary (2–3 sentences) of how the concept has changed, plus links to relevant Reference pages that explain the legacy patterns and offer migration guidance.

Agree that the Learn section should stay future-focused and beginner-friendly without assuming prior React knowledge. Still, it could really help current devs that are "stuck" in the hooks era and need a nudge toward the new mental model

that makes a lot of sense!

I also wonder if action props could be implemented in "dom apis" much like <form>'s action prop.

e.g. <button actionClick={...} />

very well explained! i'm excited to participate in the working group.

The bit about baking transitions into design components reminded me of a pattern that was going to make it into the docs but ended up being left out

No one talks about them until a browser vendor messes with them

el halftime show del super bowl va a estar épico🔥

got it! I think I understand it now after looking at the docs example

new features? Or should I say… nOt InNoVaTiVe FeAtUrEs?

if/when the React Compiler enables us to omit the dependency array, would useEffectEvent then become unnecessary?