Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I think the Github link [1] does a much better job at explaining what it is.

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

    by ksec
  • 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.
    by epolanski
  • Weren't there RedwoodJs, BlitzJs and few others that did that already?
    by atraac
  • 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
    by trueadm
  • 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?
    by xpl
  • 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

    by mcintyre1994
  • It seems like an attempt to port Svelte's features to React-like api?
    by mapcars
  • The copy reads like it is react but improved. Which begs some questions: what strings are attached and why wouldn't the authors of react adopt this? What reasons would developers have to not switch from react to octane?
    by exceptione
  • 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.
    by trueadm
  • An interesting feature is this:

    > A current-state getter. useState and useReducer return [state, update, getState], so a delayed callback can read the latest value instead of a stale capture.

    There are currently a few workarounds in React for this, and using other state management libs also give you non-reactive access to current state, but this is a big help in certain situations.

    For example, a callback / event that you pass to all your child elements, that needs to access the current state when run, therefore normally needs to be recreated with the new state captured (in useCallback) whenever state changes, which then causes all child components to re-render. Non-reactive access to current state in callbacks avoids this entirely.

    There are some hacks that fix this by wrapping the updated callback in a ref and updating it with an event (for example, https://usehooks-ts.com/react-hook/use-event-callback useEventCallback as implemented various places) and returning a stable reference to a function that calls that saved one, though I always wonder if there are downsides to this.

    by adzm
  • 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?

    by xpl
  • The Octane compiler has overlap in terms of memoization but also goes far further
    by trueadm
  • - please post 10 new frontend frameworks daily to HN

    - i ll take that over the AI, GPT, LLM, Agent stuff on HN anyday now

    by vivzkestrel
  • What, you don't like hearing about how someone used the new AI to AI an AI in order to bash something together that will never get updates?
    by Semiapies
  • I recognize this comparison style. Definitely generated by Claude. haha
    by aatd86
  • Just took a glance so I may be completely wrong, fell free to ignore, but if I understand correctly, tsrx is just syntactic sugar for normal tsx code and does not enable anything new?

    If this is the case: I think introducing tsrx as part of Octane muddies the water a bit and makes me more hesitant to try (even if it is optional).

    The idea to make tsx files more readable may be interesting but in that case it should go into its own separate project, and maybe just put a lang toggle in Octane docs and a page about tsrx compat, that way if people are intrigued by the new syntax they can just look it up but the docs stay focused.

    by Guillaume86
  • agreed, tsrx is neat as supported but personally i'm not a fan of it, makes me think of angular and more domain specific language stuff. the whole tsrx angle makes me wary of this project entirely, which is a shame, since octane does sound pretty neat. i'll still check it out, but this was indeed my initial reaction upon seeing tsrx here
    by adzm
  • Would look more appealing without the AI flavour. If you're vibe coding, do yourself a favor and write website copy yourself - it's the only evidence of human input or oversight your project will have.
    by ricardobeat
  • I still think code quality itself reigns supreme. I couldn't give less of a damn about a website.
    by throwaway27448
  • It’s especially grating in this case because Dominic Gannaway, the creator of Octane, is the real deal (creator of Inferno, former React core team member, former Svelte core team member); so the project landing page looks like generic 2026 slopcoded abandonware, but it is in fact a real project made by someone who’s one of the great minds of frontend framework development (with heavy Claude use apparently, to be clear).
    by gbjcantab
  • > 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.

    by rco8786
  • Which is ironic because the author works at OpenAI!
    by mcintyre1994