I know it's 2 years old, but it's fun to look back and see where we were, not too long ago. His #1 need is "Outstanding Unicode support", and he's switching to

I know it's 2 years old, but it's fun to look back and see where we were, not too long ago. His #1 need is "Outstanding Unicode support", and he's switching to Python for this. Just today there was a blog post that made the rounds, "The Truth About Unicode In Python" (http://www.cmlenz.net/archives/2008/07/the-truth-about-unicode-in-python http://www.cmlenz.net/archives/2008/07/the-truth-about-unico...) that gripes about Unicode in Python! One of the gripes about Python was that its internal representation is UCS-2 by default. In comparison, SBCL uses 21 bits internally, and his Python example works fine in SBCL (on the Mac, no less): * (characterp #\MUSICAL_SYMBOL_G_CLEF) T * (char-name #\MUSICAL_SYMBOL_G_CLEF) "MUSICAL_SYMBOL_G_CLEF" I wonder if he had to make the choice again on a fresh project today which he would choose. Things change fast.