I can only speak on compojure. So far I've only done some simple expermental apps using compojure and using enlive for template, clojurql for database. It's more work to make everything tie together than I'm used to. Since I use grails for production work, and have used lift for some internal apps as well. I keep looking for lazy ways to generate wars and such.
On Jul 19, 2009, at 4:24 PM, Vagif Verdi <vagif.ve...@gmail.com> wrote: > > On Jul 19, 9:49 am, Wilson MacGyver <wmacgy...@gmail.com> wrote: >> There are already two webframework in clojure being developed. >> Compojure and cascade. While I'm eagerly waiting to see how these two >> and others will envole > > Not much to wait there. Compojure is quite stable and feature rich > now. It is a low level web framework. You have to explicitly manage > urls and code html by hand, using their html combinatorics library. > There's nothing wrong with being a low level web framework. You > certainly can build up upon it. I'm currently migrating our web > application from plain java servlets to compojure. > > Cascase is not even a web framework yet. It is a toy. And sadly from > what i've seen so far, it took the same path as compojure: explicitly > dealing with urls and manually building html pages with its own > library. No high level object/widget approach a-la Seaside, Weblocks, > Rails etc. > So there's a space for different kind of web frameworks in clojure > ecosystem. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---