Octane – React's programming model, compiled

Posted by nnx 5 hours ago

Counter53Comment21OpenOriginal

Comments

Comment by ksec 2 minutes ago

I think the Github link [1] does a much better job at explaining what it is.

[1] https://github.com/octanejs/octane

Comment by rco8786 1 hour ago

> Measured, not vibes

Sort of ironic considering that there are a LOT of vibe tells in the copy throughout this page. It's a neat looking project, it's a shame that every other sentence has Claude's fingerprints all over it.

Comment by mcintyre1994 1 hour ago

Which is ironic because the author works at OpenAI!

Comment by christophilus 51 minutes ago

Yeah. I thought it sounded like OpenAI more than Claude, though maybe they’ve converged. It’s been a while since I used Claude.

Comment by trueno 43 minutes ago

claudes still claude. still as load-bearing as ever. the ladies have no idea how absolutely right i am every day

Comment by torment-nexus 12 minutes ago

This is an interesting problem. A similar approach that worked for us was to only load the tools the agent actually needs for each task.

Comment by aatd86 3 hours ago

I recognize this comparison style. Definitely generated by Claude. haha

Comment by xpl 1 hour ago

Does it have any overlaps with React Compiler — like the auto-memoization that they have?

Also, is there any read on the downsides / shortcomings / caveats of Octane vs. vanilla React?

Comment by xpl 2 hours ago

The model is a bit different from React (no deps, hooks can be under ifs) — do coding agents recognize it or they get confused when they see that code?

Comment by mcintyre1994 1 hour ago

Their llms.txt spells it all out: https://octanejs.dev/llms.txt

But it doesn't have the repeating yourself/over-emphasising that you sometimes see in LLM instructions when someone is trying to fight the model's default assumptions

Comment by mapcars 3 hours ago

It seems like an attempt to port Svelte's features to React-like api?

Comment by adithyassekhar 3 hours ago

It took a while to render when I clicked the Differences from React button on an iphone 17.

Comment by christophilus 2 hours ago

Same. I think it’s just a link, and its content took a while to load. Looks like it’s the docs site vs the marketing page.

Comment by Tajnymag 3 hours ago

I'm surprised how good Vue Vapor mode is from the performance comparison table.

Comment by purerandomness 3 hours ago

Funny how Vue Vapor 3.6 beta and Ripple 0.3 show the exact same performance (1.0) as Octane, but their bars are a tiny bit longer so the Octane team can pretend to have a justification to put their implementation on top.

Classic statistics dark pattern.

Comment by trueadm 3 hours ago

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.

Comment by epolanski 2 hours ago

Interested in experimenting with Octane, wish that docs emphasized more the SSR aspect of it, because I'm looking for a Ruby/Phoenix/Php alternative in TypeScript land, and one with React-like apis would be cool.

Comment by trueadm 2 hours ago

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

Comment by atraac 2 hours ago

Weren't there RedwoodJs, BlitzJs and few others that did that already?

Comment by trueno 30 minutes ago

theres gonna be a lot more at this rate. everyones tribalistic preferences about how web frameworks should be made... is never going to get solved. now everyone can just spend a week of their claude max plan making whatever framework they want. ive done it like twice now in the past year just for shits and giggles, it is fun but i wont pretend like i know where any of this is going, i think a hybrid of ssr and a blend of "the client should do some work" is probably the prevailing strats that will scale. something like aggrid is a very performant js datatable so i personally am not inclined to try and reinvent that from the backend, rather a backend has full coverage over its api surface but largely just sets/configures/sends data to but lets aggrid do what aggrid does. component models and diffing changes and all of that though and sending lil dom updates... shouldve never been purely on the front end to begin with. front end runtimes are about to get way smaller.

my favorite part of using whatever this weird ssr hybrid landscape ive been in is just not using graphql lol. i can just rawdog sql now for most things like the lords of data intended. its fantastic

Comment by epolanski 1 hour ago

Didn't like the apis nor both being built on top of react crap.

Comment by KoleSeise1277 1 hour ago

[dead]