The best thing with the introduction of ClojureScript, at least for web applications, is that we can now write the whole application in Clojure without context switches. Gaka for CSS, ClojureScript for JavaScript, Hiccup for HTML and Clojure for everything else. Possibly someone could design a form validation library that validates both server side and client side with the same code. Love the possibility being presented here.
Sandbar has form validation in it,though not sure if it would work for clojurescript. And personally I'd still use enlive for HTML so can buy prebuilt templates and just tweak my code to work within those, but that could just be me :)
the enlive vs hiccup battle is not really changed by ClojureScript. I am glad that we have enlive, hiccup and fleet so everybody can take whatever he wants.
Comments
The best thing with the introduction of ClojureScript, at least for web applications, is that we can now write the whole application in Clojure without context switches. Gaka for CSS, ClojureScript for JavaScript, Hiccup for HTML and Clojure for everything else. Possibly someone could design a form validation library that validates both server side and client side with the same code. Love the possibility being presented here.
Sandbar has form validation in it,though not sure if it would work for clojurescript. And personally I'd still use enlive for HTML so can buy prebuilt templates and just tweak my code to work within those, but that could just be me :)
the enlive vs hiccup battle is not really changed by ClojureScript. I am glad that we have enlive, hiccup and fleet so everybody can take whatever he wants.
Don't even know Fleet, but Hiccup certainly has a place for when you WANT code as HTML. I'd never want it but I can understand why some would.
The idea of passing around Clojure Data instead of JSON is very nice too.