Lisp for the Web, Part II

#1

Post by matthewsnyder » Sat, Jul 09, 2011, 3:50 PM UTC

Re: Lisp for the Web, Part II

#2

Post by sigil » Sat, Jul 09, 2011, 5:36 PM UTC

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

#3

Post by [deleted] » Sat, Jul 09, 2011, 5:38 PM UTC

[deleted]

Re: Lisp for the Web, Part II

#4

Post by mtraven » Sat, Jul 09, 2011, 5:46 PM UTC

Allow me to flog WuWei, http://wuwei.name, a toolkit for doing Ajax web UIs in Common Lisp, now in production use on http://biocyc.org .

Re: Lisp for the Web, Part II

#5

Post by ericmoritz » Sat, Jul 09, 2011, 6:10 PM UTC

sigil wrote: post #2

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.

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

#6

Post by ScottBurson » Sat, Jul 09, 2011, 6:47 PM UTC

mtraven wrote: post #4

Allow me to flog WuWei, http://wuwei.name , a toolkit for doing Ajax web UIs in Common Lisp, now in production use on http://biocyc.org .

How does it compare to Weblocks?

Re: Lisp for the Web, Part II

#7

Post by maximilianburke » Sat, Jul 09, 2011, 6:51 PM UTC

I've been hacking together a site using Hunchentoot, Postmodern + PostgreSQL, CL-WHO for HTML generation, and CL-JSON + Backbone.js for client interaction. I'm probably duplicating a lot of functionality that would already be done with Rails or Django but I'm having a lot of fun doing it this way :)

Re: Lisp for the Web, Part II

#8

Post by funcall » Sat, Jul 09, 2011, 7:21 PM UTC

ericmoritz wrote: post #5

sigil wrote: post #2

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.

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.

Generated JavaScript can be served and cached just like static .js files. It doesn't have to be embedded in the HTML.

Re: Lisp for the Web, Part II

#9

Post by funcall » Sat, Jul 09, 2011, 7:26 PM UTC

sigil wrote: post #2

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.

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

#10

Post by sigil » Sat, Jul 09, 2011, 7:50 PM UTC

funcall wrote: post #9

sigil wrote: post #2

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.

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]

Interesting. What's the site, and is the original Clojure source before -> js transformation published somewhere?