Rendr Rendr / asset / free

https://github.com/airbnb/rendr

Rendr is a small library from Airbnb that allows you to run your Backbone.js apps seamlessly on both the client and the server. Allow your web server to serve fully-formed HTML pages to any deep link of your app, while preserving the snappy feel of a traditional Backbone.js client-side MVC app.
0 favorites
submitted over 3 years ago, by bonzai
Rendr popular asset

4 Comments

bonzai
SkinnyGeek1010

Yeeeeaaa Booooii. This is a step towards the infamous "holy grail" =)

SkinnyGeek1010, over 3 years ago

pineapple

Can you explain why iz great for us non-backbone.js foo's

pineapple, over 3 years ago

SkinnyGeek1010

I haven't had a chance to use it yet, but some of the big wins that they're going for are:

  • Use most of your app on the server and client.

  • Flexibility. you can use it in currently running apps, and it allows you to tweak how it works. Using Meteor would require an entire re-write.

  • reduces code redundancy. It's really nice to be able to use your backbone models and views on the server... this makes it especially nice for single page apps and the first request is /users/1234 , it will send down the profile page with html loaded so there's 0 render time... there after it works like normal.

Cons:

  • it's just a library, so there's a decent a bit of work to do to get running.

  • Even with a large cup of coffee, it's still a lot to take in and grok.

I think at the very least their methodology will help pave the way to something more turn key.

Things like Meteor solve these problems rather nicely, but it seems to have even more magic than Rails, and you have to buy into the whole ecosystem they choose.

Derby solves some of the 'holy grail' type issues, but doesn't integrate with Backbone specifically. Airbnb was using Derby for some prototype projects, but I haven't talked to them recently to see if they're still using it.

Sometime with all of this rapid JS movement and complexity... it makes me want to pickup Ruby on Rails =D

SkinnyGeek1010, over 3 years ago


Login or to comment.

Tutorials are any resources you learn from.

Examples: an intro to html5 screencast, a pdf about git, photoshop effects tutorials, meta-programming in ruby, lambda calculus, higher-order fixed-point combinators.

Tools are websites, apps or services used -on- your project (indirectly), to aid the process.

Examples: A color scheme generator, email marketing software, usability heat maps, css3 code generators, a downloadable png compressor.

Assets are downloadable files used -in- your projects, usually as code, textures, or images.

Examples: a jquery sticky menu, photoshop brushes, background textures, mvc frameworks, twitter bootstrap, 960 grid system.