Phil- A little background on my clojure web experience: I've got a intranet web tool written using ring / enlive / moustache (system health / monitoring for a personal project) as well as dabbled in compojure before the 0.4.0 rev, and more recently I've been looking at sandbar / carte. The timeframe for which I last took a serious look at Clojure web technologies was April - May of this year (2010).
I'd say there were four main reasons why I chose to use rails over a Clojure based solution: 1. Personal ease of feature implementation: This is part personal past experience, part community support. I have some experience in rails, and other rails-like frameworks. As far as community goes, every problem (except the Passenger question mark problem I'm currently having) there was a googleable solution that I found, or at least a discussion that I could use to learn about the problem I was having, consensuses on best practices, etc. 2. Persistence. For that monitoring intranet app I mentioned above I'm using clojure.contrib.sql to make one-off connections to some relatively simple schemas (log entries, no relations). A moderately complex schema would have throw me for a loop using clojure. 3. Sessions using ring handlers. These were a problem for me, but I think my handler mental model is broken. 4. Ecosystem. Tons of gems, plugins. Great for getting the broad strokes down. If you're willing to continue the discussion, I'd like to keep this going (maybe another thread?). As I'm writing this I'm getting the feeling that I'm not quite articulating my thoughts well, and I think further discussion will help me to flesh them out. Again, I'm really excited about the amazing progress that's been made in the Clojure web space (even just since May). It's a tough problem to get right, and I'm definitely willing to help those that have taken up this difficult challenge any way I can. -Zack On Jul 11, 8:14 am, Phil Hagelberg <p...@hagelb.org> wrote: > On Sat, Jul 10, 2010 at 11:23 PM, zkim <zachary....@gmail.com> wrote: > >> but what do you think about using Justin's codebase, or an Aleph-based > >> server to > >> host the thing instead of Ruby/Rails? (see the link above for more details) > > > I'm inclined to move forward with the Ruby / Rails for now. The > > reason I went with rails is that (in my experience) none of the > > clojure web libraries are mature enough to do something like > > clojuredocs as quickly and easily as I personally would be able to do > > in rails. > > Could you provide details about what it was specifically that you > found was lacking? > > -Phil -- 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
