Rendr - Use Backbone on both the server and client
1–10 of 35 posts
Re: Rendr - Use Backbone on both the server and client
#2[deleted]
Re: Rendr - Use Backbone on both the server and client
#3More background and discussion about Rendr and how it fits into the stack of the nodejs app AirBnB built: http://nerds.airbnb.com/weve-launched-our-first-nodejs-app-t...
Re: Rendr - Use Backbone on both the server and client
#4The Holy Grail!
Re: Rendr - Use Backbone on both the server and client
#5I've been waiting for YUI team to fit the YUI App Framework(the equivalent of BackBone) into Mojito. But seems like you've beaten them to it. :)
Great job!
Re: Rendr - Use Backbone on both the server and client
#6I have gone through the blog post and bit of code but I am a bit stomped. Can anyone tell what is the flow here?
If I go directly to /search/q=hello, the request will go to server, it will render the HTML on server and send it to client. What happens next? Do they send all the Javascript + client-side templates alongside as well so that further requests are catered on client?
Think I should fiddle around with the sample app.
Re: Rendr - Use Backbone on both the server and client
#7I remember reading their blog post about their "Holy Grail" framework, but I couldn't really understand what made it so cool. Can someone explain to a noob like me why someone would consider Rendr the Holy Grail of frameworks?
Re: Rendr - Use Backbone on both the server and client
#8I remember reading their blog post about their "Holy Grail" framework, but I couldn't really understand what made it so cool. Can someone explain to a noob like me why someone would consider Rendr the Holy Grail of frameworks?
IIRC, it bridges single page web apps and standard websites. I.e. on the initial request, the page is rendered server-side, similarly as it would say with Rails and will work even if the client has JS disabled. If the client has JS enabled, it will work as a SPA.
Re: Rendr - Use Backbone on both the server and client
#9I don't like the idea of rendering client code in the server.
Re: Rendr - Use Backbone on both the server and client
#10I remember reading their blog post about their "Holy Grail" framework, but I couldn't really understand what made it so cool. Can someone explain to a noob like me why someone would consider Rendr the Holy Grail of frameworks?
MVC is being used for web development. The M part, model, handles the rules for inputs. This would trigger validation errors. In a typical stack, we code the server-side model in, say, Ruby on Rails, and duplicate the same model in client-side model in JavaScript so it can detect things like minimum password lengths without sending data back to the server. The holy grail is to have both server-side and client-side in JavaScript and also sharing the models as well, with that we reduce amount of things we have to code.