And yet, likely still slower than a plain Ruby on Rails app.
This is not a troll, Rails remains one of the quickest, simplest, out-of-the-box ready solutions for a web app.
Every time I am tempted to try NextJS or the JS ecosystem in general, I immediately get frustrated by the fragmentation for what is settled and standard functionality. Typescript is what keeps tempting me, but Sorbet is helping with that.
I miss Rails deeply but when I tried using it earlier this year, I was struck by how limiting the templating system is compared to React. Components, unidirectional data flow, and years of thinking in Hooks made moving back to ERB feel like a step backwards. And that’s saying nothing of the TypeScript piece.
My dream is that we’ll see Rails with React Server Components support.
The ViewComponent (viewcomponent.org) project brings a lot of the benefits of components to Rails views. It makes data dependencies explicit, it makes them testable, and reusable.
Worth checking out, but it doesn't address unidirectional data flow and hooks, since those are not relevant in a Rails context.
Personally, having state on the server and updating html over the wire is far superior to managing client-side state.
This is not a troll, Rails remains one of the quickest, simplest, out-of-the-box ready solutions for a web app.
Every time I am tempted to try NextJS or the JS ecosystem in general, I immediately get frustrated by the fragmentation for what is settled and standard functionality. Typescript is what keeps tempting me, but Sorbet is helping with that.
I would absolutely love a Typescript on Rails.