As somebody who contributes to ClojureScript, I genuinely do not understand the purpose of this project. If you want a JavaScript with Lispy syntax, there are a few things like http://lispyscript.com/ -- Spiritually similar to CoffeeScript. But if you want Clojure semantics, there is ClojureScript: Very different than a simple transpiler like CoffeeScript. ClojureScript includes a standard library of rich data struct…
Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
31–40 of 52 posts
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#32As somebody who contributes to ClojureScript, I genuinely do not understand the purpose of this project. If you want a JavaScript with Lispy syntax, there are a few things like http://lispyscript.com/ -- Spiritually similar to CoffeeScript. But if you want Clojure semantics, there is ClojureScript: Very different than a simple transpiler like CoffeeScript. ClojureScript includes a standard library of rich data struct…
I was pretty dissapointed with ClojureScript because it generates almost unreadable JavaScript; It includes an extremely heavy library that most people don't use and would never use; It depends on a lot of JVM specific things. For it to be a lot more successful as a compile-to-javascript platform it would need to move closer to native JavaScript than anything else.
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#33Earlier quoted context omitted.
Parenscript seems pretty cool. I tried Clojurescript about 2 months ago and the build process was disturbingly frustrating. :-/ I will take a swing at Parenscript next time I get on that particular project.
> build process was disturbingly frustrating that pretty much sums up my experience with ClojureSctipt as well.
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#34Does Wisp have any facility for namespaces - I didn't see anything about that in the link?
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#35As somebody who contributes to ClojureScript, I genuinely do not understand the purpose of this project. If you want a JavaScript with Lispy syntax, there are a few things like http://lispyscript.com/ -- Spiritually similar to CoffeeScript. But if you want Clojure semantics, there is ClojureScript: Very different than a simple transpiler like CoffeeScript. ClojureScript includes a standard library of rich data struct…
A primary benefit of things like Wisp is it makes it easier for non-clojure users to dive in and learn a clojurescript like language. I like JS and I like Lisps but the learning curve for clojurescript is too much if you don't know Clojure already. Wisp feels much more JS like; with my decent JS and decent Scheme knowledge I feel I could just dive in and play with it. Clojurescript does not leave me with the same imp…
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.
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#36Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#37Earlier quoted context omitted.
Seems like a disadvantage to me. It's mostly just confusing and the only thing it affords is the ability to use :keywords as functions (:like so) which is just sugar for property access, so["like"]. This is broken, though. The coolest thing about :keywords in Clojure is that they really are functions and you can do things like (map :keywords ontoSomething) to extract the same property out of many things. It don't wor…
What you're not realizing, though, is that each time you use the string "like" as a key for a map/dictionary, you're allocating a new object on the heap. So what if you have many keys, and they're all strings? What if you have many maps that share the same keys? That's a lot of memory to allocate, and strings are an extremely inefficient way to implement what is essentially a unique identifier to address map values.…
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#38Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#39As somebody who contributes to ClojureScript, I genuinely do not understand the purpose of this project. If you want a JavaScript with Lispy syntax, there are a few things like http://lispyscript.com/ -- Spiritually similar to CoffeeScript. But if you want Clojure semantics, there is ClojureScript: Very different than a simple transpiler like CoffeeScript. ClojureScript includes a standard library of rich data struct…
I agree. The comments here make me think that the commenters don't know all of the extra ideas that Clojure brings besides a "different syntax" to Lisp. Even just for the immutable, persistent data structures that support value semantics (& distinguishing state from identity), ClojureScript ought to go a long way to helping write better code.
Wisp, I guess provides readable js as opposed to compiled js. That's a win.
Re: Wisp: a homoiconic JS dialect with Clojure syntax, s-expressions and macros
#40Earlier quoted context omitted.
"without the JVM" ... "Once the JVM compiler is up" Does not compute! :P
Can't quite tell if you're serious or joking. In case it's the former: the ClojureScript compiler is implemented in Clojure, which runs on the JVM. The compiled code is Javascript, which doesn't require the JVM. There have been some discussions about making the compiler hostable from Javascript as well, but it's not possible just yet.
> ClojureScript compiler is implemented in Clojure, which runs on the JVM