Love this.

This is actually quite timely for me. An app I am trying to build, involves a lot of real-time stuff and have been debating whether or not I should go to a client-side MVC. I am not too gung-ho on doing it, largely because at the core a lot of the functionality of the app is simple CRUD stuff. Then just a matter of updating elements of the app in real time.

Is there a gem for Socket.IO?

Yes. https://github.com/lyondhill/socket.io-ruby-client

Is this what you guys used, or did you use the regular client in some other way?

That is what we use in production.

Use sockjs instead of socket.io :). There is a rails gem for it, or you could use ruby on top of vert.x which also supports sockjs.

Great work Kelly. How much browser pain have you all had with data-attributes?

So far, no browser pain at all with the data-attributes.

When dealing with numbers, you will often find yourself making many calls to parseInt(). Other than that, it's smooth sailing.

Great thanks. So cool to see what you have done since the days at AutomaticDuck.

Where is your production app hosted? Heroku? AWS? Your own colo box?

We use Slicehost.