News for hackers. Stuff that matters.
Re:Lisp for the Web, Part II by sigil on Saturday July 09, 2011 @01:36PM (#2745941)
Great article! The only thing I'd do differently is just serve up the js as a static file instead of using code transformation. That seems likely to break for non-trivial amounts of js.
Re:Lisp for the Web, Part II by funcall on Saturday July 09, 2011 @03:26PM (#2746171)
I beg to differ. I've used ClojureJS (a Clojure to JavaScript translator) for building a non-trivial web app front end, and the result has not only been robust but also a pleasure to build (from a Lisp programmer's point of view).

[Disclosure: I'm the author of the ClojureJS library]

Re:Lisp for the Web, Part II by sigil on Saturday July 09, 2011 @03:50PM (#2746227)
Interesting. What's the site, and is the original Clojure source before -> js transformation published somewhere?
Re:Lisp for the Web, Part II by funcall on Saturday July 09, 2011 @04:29PM (#2746292)
We're not launched yet (but, close). I'll definitely post about it when we're live. I'm not sure how much of the Clojure (subset) code we'll publish, but I'll write more about our process and experience once we're launched.
Re:Lisp for the Web, Part II by ericmoritz on Saturday July 09, 2011 @02:10PM (#2746020)
Yeah, Generate the data (JSON) that the javascript will work with, don't generate the javascript. That way we can have easy to serve, easy to cache static javascript.
Re:Lisp for the Web, Part II by funcall on Saturday July 09, 2011 @03:21PM (#2746162)
Generated JavaScript can be served and cached just like static .js files. It doesn't have to be embedded in the HTML.