setState during render which we felt wasn't very usable or scalable by both humans and agents. We also have a "use strong" mode for Octane that literally bans, at a compiler level, setState in the render phase for either the entire project or specific modules.

We're also exploring using "use strong" to ban setState in effects, with error messages that tell the agent to move it to a better location – such as the event handler or the right place in your design system.

we know that humans get emotional about these choices, but if you're not the one making the changes, then having an agent deal with the constraints means better code in general.

Octane's useLinkedState solves synchronization state problem. No option from React 🤷‍♂️

#octanejs #setState #useLinkedState