I don't see the point in this as a serious production language. As a project to just have fun, of course it is a cool idea.
Lisp systems moved to generic functions for a reason - Lisp dialects for some time used a Smalltalk-based message sending model, but it just isn't as flexible.
But if the desire is to get Ruby semantics with Lisp syntax, I think the much more reasonable approach is to run a Rubyesque Lisp on Rubinius (which the lead devs have already talked of doing). At least by doing that you get the advantage of piggybacking on an advancing VM and a language that already has libraries.
Lisp systems moved to generic functions for a reason - Lisp dialects for some time used a Smalltalk-based message sending model, but it just isn't as flexible.
But if the desire is to get Ruby semantics with Lisp syntax, I think the much more reasonable approach is to run a Rubyesque Lisp on Rubinius (which the lead devs have already talked of doing). At least by doing that you get the advantage of piggybacking on an advancing VM and a language that already has libraries.
Establishing a new language is hard.