Rules changed. Teams choose which country they represent, and one member needs to be a citizen of this country, but others can be from anywhere. Yay!

Thank you!

Author of the blog post here.

I think interfacing functional code from object-oriented code is usually pretty easy. You just wrap the functions to an object instance.

However, if your 'outer layer' is functional, and try to integrate OO pieces inside it, it can be troublesome to to wrap your OO code in such a way that it's natural to use in a functional context.

OO paradigm is in some sense more restricting, in that it limits the client of the code to using OO-like patterns.

Does this make any sense to you?

On a related note, this recently trended article does a good job of explaining what state machines are: http://blog.markwshead.com/869/state-machines-computer-scien...

An clean way to implement finite-state machines is Akka FSM [1]. I recently wrote a blog post about it: http://news.ycombinator.com/item?id=3976558

[1] http://doc.akka.io/docs/akka/snapshot/scala/fsm.html

Nothing too fancy, but makes my own Google Reader experience a lot better.