Re:Wisp: a homoiconic JS dialect with Clojure syntax, s-expr...
by kyllo on Friday May 24, 2013 @02:36AM
(#5761527)
Yeah, I think the concept of sticking a JVM in the middle of the process of generating browser scripts is very strange. Clojure has a lot of JVM specific quirks that don't make sense in the context of Javascript at all. And if you're coming from another Lisp/Scheme dialect, Clojure is definitely nontrivial to learn.
Wisp looks like Javascript was supposed to look before they bolted C syntax onto it. People say that Javascript is like Scheme with C syntax. So Wisp is like Javascript with Scheme syntax. I think this is something I would actually use.
I didn't know about LispyScript either, though. I would have to compare/contrast the two.
Clojurescript's heavy dependence on the Clojure environment (JVM, leinigren etc) make it a real pain to get setup for. I have looked into clojurescript several times but thought "I better master clojure first". I have been getting a hang of Clojure slowly and plan to tackle learning clojurescript eventually but something like Wisp opens up the possibility of diving in without needing to be comfortable with all the Java crap.
I only tend to take up something when it takes me five minutes to start learning. I think most are the same way; it's the reason why Codecademy is so popular and why clojurescript's primary user base is Clojure users. The more users that can start learning a language in five minutes the better it is for that language. Clojure beat out other Lisp implementations primarily because it was easier to dive into for a greater number of humans than any other Lisp.
Wisp and other implementations like it make diving into Lisp->js languages much easier. It removes the large roadblock that is Java, a roadblock that is unnecessary if your target language is JS not Java.