Post

Happy to announce Octane – the successor to Inferno. React’s programming model, compiled. Hooks, Suspense and Actions, compiled ahead of time. No virtual DOM. No Rules of Hooks. No manually maintained dependency arrays. The compiler understands what your code. octanejs.dev

The dependency array removal is the part that actually changes the authoring experience. Curious how the compiler handles cases where the reactive closure captures a value that shouldn't trigger re-execution - does it infer stability from usage, or is there an escape hatch when it gets it wrong?

It does infer usage based off a few things. There's likely more wiggle room here. You can always opt to put them in manually if you want too. Any feedback on how we can make them better is highly valued as a github issue. :)

0 reposts0 likes

Good to know the manual override is still there. The inference approach sounds practical for the common cases, and having GitHub issues as the feedback path makes sense for surfacing the edge cases that come up in real usage.