> has a parallel elegant solution in Ruby (using blocks, dynamic method definition, or otherwise) > Sometimes with lisp things get "spooky" in a way that just

> has a parallel elegant solution in Ruby (using blocks, dynamic method definition, or otherwise) > Sometimes with lisp things get "spooky" in a way that just doesn't happen in practice with Ruby Over here the long run practical experience with Ruby on a couple or three significantly involved codebases and assorted dependencies taught me over the years that such solutions are elegant for a month then end up being a hell to maintain, debug, and trace through. We definitely encountered my lot of "spooky" things in Ruby-land. For maintainable code on the long run we now vastly favour boring, non-dynamic, explicit, down-to-earth code. Dynamic solutions, DSLs or dependencies making use of those now therefore have to sustain solid justifications and heavy scrutiny before being greenlighted.