3 ms·
I'm working with these libraries for a web project now, and I'd say the main problem is lack of comprehensive documentation. If you're doing something slightly
by danenania 13y ago
I'm working with these libraries for a web project now, and I'd say the main problem is lack of comprehensive documentation. If you're doing something slightly off the beaten path and get stuck, it's quite likely that you'll have to resort to the source code to solve your problem.
There's nothing so terrible about that per se--it's a great way to learn--but it can feel like a high friction workflow compared to Rails, especially getting started. I think it's primarily a function of community size and library maturity, but there's a cultural element as well. Rails has more of a beginner-friendliness-is-good mindset (even when library internals are fugly), while in Clojure the focus is more on the strength of the functionality and less on easily grokkable apis (though there are notable exceptions).