Earlier quoted context omitted.
There are a LOT of in-browser scheme-like variants.
A few are listed here: https://github.com/jashkenas/coffee-script/wiki/List-of-lang... (which also includes Clojurescript)
ClojureScript
21–30 of 95 posts
Re: ClojureScript
#22I'm wondering if this has the refs, agents, and atoms that make concurrent clojure so awesome. If not, it would feel.... strange.
The impression I got is the core syntax is all there, you just don't get access to the jvm libraries anymore.
Re: ClojureScript
#23Earlier quoted context omitted.
There are a LOT of in-browser scheme-like variants.
A few are listed here: https://github.com/jashkenas/coffee-script/wiki/List-of-lang... (which also includes Clojurescript)
Re: ClojureScript
#24Earlier quoted context omitted.
I don't understand; why bring a web framework into it for command-line work? Is it just that straight-up V8 has a crappy CLI experience?
Web framework? Do you mean Google Closure? If so, bear in mind that the compilation phase will remove unused code, so you're not forced to carry any of it with you if you never use it in your code. As for Node, you do not need it I suppose, but I do not have experience using straight-up V8.
Re: ClojureScript
#25Earlier quoted context omitted.
The impression I got is the core syntax is all there, you just don't get access to the jvm libraries anymore.
All of the core syntax is not currently there, but you're right that ClojureScript only interops with js and not Java. For a more detailed differences list see https://github.com/clojure/clojurescript/wiki/Differences-fr...
Ack no transients either! I know it's early but not gonna lie that one makes me sad. I love being able to write stupid fast list/map builder functions that bash inline but then return something nice and immutable.
Re: ClojureScript
#26Earlier quoted context omitted.
The impression I got is the core syntax is all there, you just don't get access to the jvm libraries anymore.
All of the core syntax is not currently there, but you're right that ClojureScript only interops with js and not Java. For a more detailed differences list see https://github.com/clojure/clojurescript/wiki/Differences-fr...
Re: ClojureScript
#27Node.js + clojurescript just came up in the Demo. Part of me says awesome, another part says "How many hipster programmer brains blew up" Overall I'm excited about this and anxious to see how far it can be taken, because if you can write an ENTIRE webapp in clojure is thought provoking.
jordan shoes $32nike shox $32Christan Audigier bikini $23 Ed Hardy Bikini $23Smful short_t-shirt_woman $15ed hardy short_tank_woman $16Sandal $32christian loubo utin $80 Sunglass $15 COACH_Necklace $27handbag $33AF tank woman $17puma slipper woman $30
===== http://www.fullmalls.com =====
===== http://www.fullmalls.com =====
===== http://www.fullmalls.com =====
===== http://www.fullmalls.com =====
===== http://www.fullmalls.com =====
Re: ClojureScript
#28Earlier quoted context omitted.
Web framework? Do you mean Google Closure? If so, bear in mind that the compilation phase will remove unused code, so you're not forced to carry any of it with you if you never use it in your code. As for Node, you do not need it I suppose, but I do not have experience using straight-up V8.
Right, I was talking about node. It sounds like perhaps node has had more people polishing the command-line tools? Stuff that probably belongs in V8, but goes in node because it's a more openly-developed project? The mention of node just seemed a little out of place at first glance.
Re: ClojureScript
#29Earlier quoted context omitted.
I don't understand; why bring a web framework into it for command-line work? Is it just that straight-up V8 has a crappy CLI experience?
Web framework? Do you mean Google Closure? If so, bear in mind that the compilation phase will remove unused code, so you're not forced to carry any of it with you if you never use it in your code. As for Node, you do not need it I suppose, but I do not have experience using straight-up V8.
Re: ClojureScript
#30I'm wondering if this has the refs, agents, and atoms that make concurrent clojure so awesome. If not, it would feel.... strange.
Atoms are there. The others are not, but they would be pretty much meaningless in a Javascript engine anyway, since Javascript is specified to be single threaded.
They have no shared state though, not sure if that is a problem in this case or not.