> Did you implement the whole Clojure.core?
Not all of clojure.core is implemented -- a list of what's implemented is available at http://vickychijwani.github.io/closer.js/spec_runner.html?sp....
> Good work!
I'm looking forward to when they make the UI properly support it. They haven't changed much in the UI other than letting you type code in other languages. My issues:
2. New levels don't have the default code be other languages.
3. editor "Smart Behaviors" (in Editor Configuration) doesn't work in Clojure. When I type an opening parenthesis, there is no closing parenthesis automatically inserted.
5. Errors aren't especially useful. In Clojure, typing "(.attackNearbyEnemy)" results in "parse error: expecting IDENTIFIER, COLON, ANON_ARG..." Obviously, this is a hard problem, but I'd rather see something like "you called a one-argument function with zero args".
6. In Emacs keybindings, if point is at the a line with text in it, C-k doesn't delete the newline character, moving the next line to the end of the current one -- it does nothing.
These are all things I expect to be fixed soon. There's a lot of work to be done to add multi-language support, and it's awesome it's getting done.
 - http://us3.campaign-archive2.com/?u=c86c5e56e46659873417a8f1...
Your 'Nodes' file shows a strong familiarity with what's going on inside Coffeescript, too. :)
> There are a couple of other projects like this. Are you familiar with Wisp or Outlet?
The thing is, Closer was created for use on CodeCombat, which expects the parse tree to be in the standard Mozilla AST format . As far as I know, none of the projects you mention satisfy this requirement.
> Your 'Nodes' file shows a strong familiarity with what's going on inside Coffeescript, too. :)
Actually it was lifted verbatim from  -- I just converted it to CoffeeScript :)