It's basically as advertised, RoR for Node.js. This means it has an ORM, has scaffolding, etc. Looks like it takes advantage of express.js and is an abstracti

It's basically as advertised, RoR for Node.js. This means it has an ORM, has scaffolding, etc. Looks like it takes advantage of express.js and is an abstraction over it. Personally, this was how I was creating sites 3 years ago. I made my own framework that does pretty much the exact same thing. I've completely dropped this in favor of using bidirectional message passing, because imo that's what Node really excels at and it's not something you can get with RoR. If you are using Node.js, it's a good thing to have a framework that does bidirectional real-time communication out of the box. I'm not sure if tower.js supports this or not. At a very basic level, this is all I need to think about in terms of the API to get some data passed around in my current workflow. I've yet to find something more suitable for myself personally. CLIENT (mobile or web) // request data request = messenger.request('get me a list of things', message); request.success (response)-> // listen for events from server messenger.on('someone got something', (message)-> SERVER // listen for data messenger.on('get me a list of things', (message)-> message.reply(data) // emit data messenger.send('someone got something', data)