News for hackers. Stuff that matters.

A comment on Our First Node.js App: Backbone on the Client and Server. Parent comment

Re:Our First Node.js App: Backbone on the Client and Server by ianstormtaylor on Wednesday January 30, 2013 @04:18PM (#5141818)
You're missing the part about how single-page, client-side apps are much more performant _once_ the page loads. Spike is trying to get the best of both worlds (hence "Holy Grail").

Server-side gives you fast page load times. Client-side gives you fast user interaction times.

[ Parent | on HN ]
Re:Our First Node.js App: Backbone on the Client and Server by dnajd on Wednesday January 30, 2013 @06:26PM (#5142461)
That was the straw man I was thinking I saw in the post.

Why not use rails to load the page (no BYO framework involved) and then use javascript/backbone/etc on the client-side; as opposed to bringing the client-side technologies server-side to accomplish the same thing?

I'm thinking specifically of the search page example that was represented as a screenshot in this blog.

[ Parent | on HN ]
Re:Our First Node.js App: Backbone on the Client and Server by frontendbeauty on Wednesday January 30, 2013 @06:23PM (#5142443)
Exactly.
[ Parent | on HN ]