Clojurians Log v2

It's amazing now, working with Ruby, how needlessly complicated the language is. You have objects. And you have methods. So you declare these methods on the class of that Object. But then you have the reflection API. And now you need .instance_method, that captures an UnboundMethod from the class, or .method which captures a Method from the instance Sure, but classes can have methods (they are called static methods in Java). So you declare them... in classes. But the class is the instance. So you now have a .singleton_class methods that lazily creates a "class" for the "class" of an "object". Also, inside the class but outside a method is a valid place to run code - so you can define an API that dynamically declares methods too, and they can be bound to a different class than the one you're running now... Finally, there are at least two ways of declaring methods - both declare new scopes, but one is also a closure, which keeps variables from outside your method declaration. Good luck finding reason around that...