41–50 of 95 posts
Given a radical departure from the JavaScript core (comparing to Coffeescript), I wonder how easy the debugging would be.
Now we have a "solid" Lispy alternative to imperative languages that compile to JS. Nice surprise Rich !
There are a LOT of in-browser scheme-like variants.
It's interesting how closely tied to Google Closure this is. I wonder if that will present issues in the future. Regardless, ClojureScript has definitely made really smart use of it.
Given a radical departure from the JavaScript core (comparing to Coffeescript), I wonder how easy the debugging would be.
Earlier quoted context omitted.
A few are listed here: https://github.com/jashkenas/coffee-script/wiki/List-of-lang... (which also includes Clojurescript)
That ClojureScript is the (mostly experimental & now obsolete) work done by Chris Houser quite some time back. These two are not the same thing.
Edit: Now they are both on the list. Gotta love Github's wiki.
Earlier quoted context omitted.
I notice you keep replying about Parenscript, but the difference here is important. The reason this is a bigger deal than you make it out to be is because Clojure is hosted on the JVM. That means it's generally had a chance to enter the enterprise, and beyond that, has access to the entire JVM library and interop. What this means now is, for the first time, you can write Clojure code on the server, interop with legac…
To play devil's advocate, wouldn't the exact same thing be possible with the above alternatives and Armed Bear Common Lisp? You can write full-stack in Common Lisp, it's just that different parts need to go through different compilers/interpreters/transformers/what-have-you. Just as it is with Clojure. No, I think the thing to note here is that Clojure--for reasons I can only guess at--has a lot more sex appeal than…
Just because people are excited about developments in the Clojure ecosystem doesn't mean they aren't excited you can do this elsewhere. It's interesting right now because it's new, and it opens up some new ways of development for people who enjoy writing software in Clojure.
It's interesting how closely tied to Google Closure this is. I wonder if that will present issues in the future. Regardless, ClojureScript has definitely made really smart use of it.
I presume Closure is only being used as a post-processing step to optimize the javascript that's produced.
Earlier quoted context omitted.
I notice you keep replying about Parenscript, but the difference here is important. The reason this is a bigger deal than you make it out to be is because Clojure is hosted on the JVM. That means it's generally had a chance to enter the enterprise, and beyond that, has access to the entire JVM library and interop. What this means now is, for the first time, you can write Clojure code on the server, interop with legac…
To play devil's advocate, wouldn't the exact same thing be possible with the above alternatives and Armed Bear Common Lisp? You can write full-stack in Common Lisp, it's just that different parts need to go through different compilers/interpreters/transformers/what-have-you. Just as it is with Clojure. No, I think the thing to note here is that Clojure--for reasons I can only guess at--has a lot more sex appeal than…
possible with the above alternatives and
Armed Bear Common Lisp?
Node.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.
I'm glad for the Clojure community if this didn't exist before, but I'm pretty sure Lispers (ie Common Lispers) have written "entire" web apps in Lisp for quite a while[1]. For example, Kenny Tilton wrote a Lisp wrapper to qooxdoo on top of his data-flow library (Cells). The only time we need to write JS code now is for additional glue for widgets or functionality we haven't wrapped yet. And since it wraps qooxdoo, t…