> Measured, not vibes<p>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.
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?<p>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).<p>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.
I recognize this comparison style. Definitely generated by Claude. haha
I think the Github link [1] does a much better job at explaining what it is.<p>[1] <a href="https://github.com/octanejs/octane" rel="nofollow">https://github.com/octanejs/octane</a>
Why are people still building these frameworks? Can't we just use LLMs to build the best JS framework?
Does it have any overlaps with React Compiler — like the auto-memoization that they have?<p>Also, is there any read on the downsides / shortcomings / caveats of Octane vs. vanilla React?
This looks like an interesting project but reading these AI slop web pages is so exhausting. At least turn your brain on long enough to explain what your project does
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.
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?
It seems like an attempt to port Svelte's features to React-like api?
It took a while to render when I clicked the Differences from React button on an iphone 17.
I'm surprised how good Vue Vapor mode is from the performance comparison table.
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.
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
Weren't there RedwoodJs, BlitzJs and few others that did that already?
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.<p>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
Didn't like the apis nor both being built on top of react crap.
[dead]