On Tue, Jun 29, 2010 at 11:02 PM, Jason Smith <ja...@lilypepper.com> wrote:
> One of the great strengths of Clojure, and what is going to make it > hard for students who aren't already comfortable with Java, is that it > not only integrates with Java, it depends on that integration. So you > have to know a lot about Java just to get started. > I hardly know any Java and I've been using Clojure for my own small projects for 2 years now. > THEN you start adding in immutability, macros, concurrency, STM, etc. > You may not have to cover the harder things right away, but you have > to cover some of it, and this is in addition to the things that > Clojure the language assumes you already know about Java. > I've hardly touched the concurrency features in any of my own projects. I've used atoms and agents and rarely bother with the STM. I've only recently begun to understand the benefits of immutability in pratice. You don't need to know how to write a macro to reap their benefits. As far as Java you *used to* need to know something about the basic JVM flags and the classpath. With lein, clj, and to some degree, IDEs, you can mostly pretend they don't exist. > So I'll say it again, it's just not that simple. Unless you already > know Java, and the only learning curve you face is the new features in > Clojure. Then it's not bad. But it does give you new ways to cut your > foot off more quickly. :-) > I dunno I find Clojure pretty simple and that generally you pay (cognitively) only for what you use. -- 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
