I think that this is an interesting area. We can support just about any style in an existing programming language, but there are often rough edges. This remin

I think that this is an interesting area. We can support just about any style in an existing programming language, but there are often rough edges. This reminds me of how I used to mimic OO in C years ago. At a certain point you realize that you have to forgo certain things to help the person coming after you avoid making mistake -- often they do not see the ramifications of your conventions. I see this in Ruby right now when I write in a functional style. The code is often terse yet easy to read, but the lack of lazy evaluation makes it far more memory consumptive than code written in a straightforward procedural style. If you know you are making the tradeoff, it is fine. For many people, it is too subtle.