RUG::B

My name is Sergio, some of you know me, some others don't ;) I'm a Spanish Ruby developer living in Berlin for around a year now, and I want to make my first presentation at RUG::B in the next meeting if possible.

I'd like to make a review about what is laziness (or its slightly less cool but far more accurate name, lazy evaluation) in programming. Also, why is it cool, why is it useful sometimes. In what languages do we find it, and what can we do with it in Ruby. That's it :)

At Geddit we have a whole lot of realtime UIs. Lots of users change our models, which changes our views, which needs to be reflected in the browsers of lots of other different users - instantly.

There are a variety of ways of communicating in real time between the server and the client. We use PubNub, but there are other services that'll do it in different ways - and Rails 4 brings server-side events and live streaming - but beyond the communication protocol how does this fit into the Rails world where the lines between M, V and C are clearly demarcated and lovingly adhered to? How do you deal with views that change between requests? Where does the logic sit to handle models' changes that will cause dependent views to change?

In this talk I'll go into how we solved this problem at Geddit and how we think this pattern can fit into Rails in general.

A little introduction to Rails Girls Summer of Code by Carla, you can find out more at the home page