`useLinkedState` was created to avoid doing `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
Octane is far more than a "faster" version of React. Inferno tried to be that – and it succeeded to some extent too – it powered Facebook KaiOS to hundreds of millions of users in production, for low-end devices that needed the low memory usage and high performance.
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 captures and
![// Counter.tsrx — hooks next to output, no rules of hooks
import { useState, useEffect } from 'octane';
export function Counter(props) @{
const [count, setCount] = useState(0);
// A hook behind a condition is fine — slots are
// assigned by call site, not call order.
if (!props.paused) {
useEffect(() => {
console.log('count is now', count);
}); // the compiler infers [count]
}
<button onClick={() => setCount(count + 1)}>{'Count: ' + count}</button>
}](https://pbs.twimg.com/media/HOPoguXXAAAEnKq?format=webp&name=medium)