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

Re:Our First Node.js App: Backbone on the Client and Server by frontendbeauty on Wednesday January 30, 2013 @03:39PM (#5141628)

It sounds like you are really questioning the usefulness of client-side JS apps in general. Certainly not every app makes sense to be a "single-page app". But if you are creating a single-page app, then why not also allow it to render on the server?

I like to think of Rendr as just another Backbone app, that happens to be able to serve HTML from the server as well.

[ Parent | on HN ]

Re:Our First Node.js App: Backbone on the Client and Server by dnajd on Wednesday January 30, 2013 @06:30PM (#5142474)

There is the straw man again. If you are creating a completely client side app and you find it's better to have some work done on the server side... why not use mature existing server side technology along with client side technologies. It's not a one or the other scenario.

Why work hard to move client-side technologies to the server? javascript is not so good that I want it on the server-side. And server-side lanaguages are not hard to learn or hard to find people that know how to use them.

[ Parent | on HN ]

Re:Our First Node.js App: Backbone on the Client and Server by efnx on Wednesday January 30, 2013 @04:22PM (#5141834)

Yes, I think I am too. I can see the need for a single page apps for really immersive applications like games or possibly for very small targeted applications like reading mail, or showing stats, but in the case of the latter you probably wouldn't run into ten seconds worth of loading scripts.

I think I'll understand when I run into the problem Rendr solves...

[ Parent | on HN ]