Unfortunately most professional Ruby work is still done within the Rails framework these days, which more or less binds you to a more traditional OO type style.

Unfortunately most professional Ruby work is still done within the Rails framework these days, which more or less binds you to a more traditional OO type style. I do find that in regards to everything other than class/object abstraction my coding style gets more and more functional. Especially when working in a team environment though it's important to stick to some established standards and idioms... That said, Ruby itself gets more functional with each release, but it would seem unlikely that it'll ever completely shed it's OO-ness. Rambling aside, some great links. http://moonbase.rydia.net/mental/writings/programming/monads-in-ruby/00introduction.html http://moonbase.rydia.net/mental/writings/programming/monads... http://www.khelll.com/blog/ruby/ruby-currying/ http://www.khelll.com/blog/ruby/ruby-currying/ http://nex-3.com/posts/43-fun-with-the-y-combinator-in-ruby http://nex-3.com/posts/43-fun-with-the-y-combinator-in-ruby