I actually don't mind this problem much, although that might be my "functional programming" bias. You only really need a "canonical" way to do things if you wi

I actually don't mind this problem much, although that might be my "functional programming" bias. You only really need a "canonical" way to do things if you will be wanting to use features that depend on your classes being implemented in a predictable way. For example, class inheritance or implementing "super" method functionality. > I haven't even dared to touch trying to use it for polymorphism. Its not at hard as it sounds, since you have first class functions and closures. You can often handle functions directly instead of needing to create objects for everything.