News for hackers. Stuff that matters.
Re:State of Clojure 2015: Survey Results by bad_user on Thursday January 28, 2016 @03:58PM (#10991274)
> For backend web development Rails is still miles ahead of any Clojure workflow.

If by web development you mean building frontends to a relational database. If on the other hand you mean web services, then I think Rails really sucks.

Re:State of Clojure 2015: Survey Results by zubairq on Friday January 29, 2016 @01:13AM (#10993795)
I've also built a Rails like system in Clojure which has easy SQL backend support. I actually find Clojure much EASIER than Rails backend, so I definitely disagree:

https://github.com/zubairq/AppShare

Rails is just such a different thing. Rails IS really is a framework optimised for the days of Page based web applications with small amounts of Ajax requests. Clojure is much more suitable to full web applications (SPAs)

Re:State of Clojure 2015: Survey Results by dkersten on Friday January 29, 2016 @07:04AM (#10994723)
If by web development you mean building frontends to a relational database.

In my opinion, yada[1] will change this with its concept of resources (eg it already has File and Directory resources for serving static data, but it wouldn't take much to develop a CRUD/DB resource - in fact, I spoke with Malcolm Sparks (the yada dev) about this).

I personally find the Clojure(Script) development experience, with figwheel, much better than my experience with both Flask and Django (never used Rails).

[1] https://github.com/juxt/yada/

Re:State of Clojure 2015: Survey Results by AlwaysBCoding on Thursday January 28, 2016 @05:48PM (#10992090)
Hm, I guess that's a valid point. I normally think of web apps as a frontend to a database, but could see why that's not the only use case. If you don't have a database associated with the service, can't you just use AWS Lambda or something? Is it necessary to maintain an entire separate project for it?