trueadm

I mean I created Octane coming from being one of the authors of React from years ago. Octane makes breaking changes compared to React to improve on things that aren’t that important in 2026. For example the synthetic event system - which takes up 13kb of React’s payload and adds overhead over just using the correct DOM events.

The Octane compiler has overlap in terms of memoization but also goes far further

We’ll address the website content :) thank you for the feedback

TSRX allows for better runtime generated guarantees, especially around loops which generates faster runtime logic from it. We can’t assume too much statically when reading something.map as the method might have different heuristics

We’re looking to address the feedback with the website copy. Thank you for the feedback!

It has all the same SSR APIs as React. The Octane website is rendered with Octane and the source is in the GitHub repository if you’re interested to see how it works

We just run a script that runs the benchmarks and updates the chart. It’s rounds numbers too. We’ve been as honest as possible in all the benchmarks - there’s no point in lying about a metric.

It's a relatively new domain, so corporate DNS servers are likely to block it.

There is definitely a bug there, I'll put up a fix in a bit. Thanks! :)

I contributed to React and Svelte on their core teams for years. Sometimes you just need to break free

It was a good time for change, I was working on Svelte 5 non-stop for two years! I'll be announcing my new role nearer the time :)

Please can you create a Github issue with the security holes you've found? That would be greatly appreciated. I've given it a sweep and found nothing.

I left Vercel a few weeks ago and I left the Svelte team earlier this year.

I work on Svelte 5 and I was also a React engineer on the core team previously FWIW.

You can set the direction of the ElementNode explicitly to define LTR/RTL semantics. By default it’s automatically detected.