I had the opposite experience. It's pretty obvious how to do anything in Clojure. I don't need to hunt down magical incantations to use libraries like I had to in Ruby.
I started Clojure for web development. Once I found out about the Compojure template, everything else was just a stone's throw away.
$ lein new compojure myapp
$ cd myapp
$ lein ring server-headless
Server started on port 3000
I wager the average HN reader could run with that.
> There's no Rails-like framework that makes things
> 'just-work' waiting for you.
That's actually what stifles the productivity of Rails projects I've worked on. It's why I started looking at other solutions and why the simplicity of Clojure pulled me over.
rails g devise:install
rails g devise user
rails g devise:views
Nobody really knows what just happened. Things kinda work til the answers to your questions can't be pasted from Devise's wiki anymore.
> because you have to learn every little piece at a low-level to
> ever make anything happen.
Maybe we have different things in mind, here. The alternative to this in my experience is an application where nobody actually knows, for example, what's being put into the cookie, when it's put into the cookie, what part of the session is serialized in the DB, if the cookie is signed, etc.
At least that's how it was at all the Rails projects I worked on.
https://github.com/ring-clojure/ring/wiki was refreshing. It turns out that managing your own session/cookie/authentication lifecycle in your own application code is easy. And it turns out that these "it just works" generators doesn't actually save any time because when you want to make trivial changes to them, you have to credentialize in yet another abstraction.
I started Clojure for web development. Once I found out about the Compojure template, everything else was just a stone's throw away.
I wager the average HN reader could run with that. That's actually what stifles the productivity of Rails projects I've worked on. It's why I started looking at other solutions and why the simplicity of Clojure pulled me over. Nobody really knows what just happened. Things kinda work til the answers to your questions can't be pasted from Devise's wiki anymore. Maybe we have different things in mind, here. The alternative to this in my experience is an application where nobody actually knows, for example, what's being put into the cookie, when it's put into the cookie, what part of the session is serialized in the DB, if the cookie is signed, etc.At least that's how it was at all the Rails projects I worked on.
https://github.com/ring-clojure/ring/wiki was refreshing. It turns out that managing your own session/cookie/authentication lifecycle in your own application code is easy. And it turns out that these "it just works" generators doesn't actually save any time because when you want to make trivial changes to them, you have to credentialize in yet another abstraction.