Hacker News Reader

Comment by whatshisface | Hacker News Reader

I think a lot of people are now used to seamless interaction and realtime data updates. Also, pricing models on cloud service providers increasingly discourage serving from rails or nodejs, and encourage static files that offload as much as possible to the end user's device.

View on HN

You can have those interactions on Rails just like anywhere else. Cloud compute is also absurdly cheap at scale today compared to the past.

How do you manage page-wide data consistency in Rails without a page refresh?

You make sure you're only trying to do frameworkless development on pages where "data consistency" means "the text box displays the text that's in the text box." :-)

There’s multiple approaches. Since everything is server side rendered, you can for example, stream updates through web sockets

Sounds like a lot of latency, waiting for the backend to render a template and send it over the wire every time the user presses a button.

You don’t re render a template. Only what you need to. If it’s a single div then so be it. Which is why it’s SPA-like experience with server side code

And where does that new div come from? It's not a backend template?

In my understanding template would be the entire page. So while an an individual div re-rendering is also technically a template, it's not really the same thing. It's a tiny re-render compared to a page refresh.

Again, this is a different spin on doing things. Rails preaches abandoning the over-complexity of the client-side in the browser and pushing work to the server.

I personally love it. I'm sure someone who is as fast in React as I am in Rails is laughing reading this.

You're going back in forth about whether the html re-render that's sent back over the wire is always the entire page or only the specific element needed.

Hotwire

Reply on news.ycombinator.com