3 ms·
I was a full-time Rails developer until a crescendo of disillusionment finally cajoled me to learn Clojure. I don't really know that I miss anything. The thing
by danneu 13y ago
I was a full-time Rails developer until a crescendo of disillusionment finally cajoled me to learn Clojure.
I don't really know that I miss anything. The things I might've thought I'd miss are the things that ended up souring the taste of Rails.
Having to come up with my own abstractions or recreate familiar conventions or set up a database were areas where I had to cut my teeth, but I also had to cut my teeth on Rails when I was learning it.
Rather than missing anything from Rails, I find myself using Rails' conventions as a loose model and then simplifying it. For example, my "templates" are now just functions that render html. My "layouts" are just functions that get applied to templates. I don't need to read Rails' template rendering guide to come up with a hack. Instead, modifying my templating system is trivial and obvious.
- nikatwork 13y agoThank you for this comment. I'm starting a hobby webapp project and wanted to try Clojure but was probably going to choose RoR out of fear. Now I'll use Clojure :) Would be interesting to see a blog post demo'ing your workflow.
- adambard 13y agoNot the parent, but I went through a phase of blogging about Clojure earlier this year: http://adambard.com/blog/Getting-started-with-Clojure-web-apps/ http://adambard.com/blog/Getting-started-with-Clojure-web-ap...
- girvo 13y agoI agree with my sibling, would love to know about your Clojure workflow/arch more!