I don't think your tone is very helpful Armando. It's perfectly reasonable to ask for specific examples - so that there are actionable tasks we as a group can take on, rather than just some vague "the documentation is too Java-centric" complaint.
When I read the OP, I was not sure what he was really complaining about or asking for. I don't agree with the assertion that all the documentation assumes Java knowledge - and clearly a lot of non-Java programmers have managed to pick up Clojure just fine. Even tho' I have Java experience, I had no experience with Maven so the whole library dependency thing was new to me - but it didn't seem Java-centric. I had experienced the classpath aspect of Java but, frankly, Leiningen completely hides that. The only "required" Java experience, as far as I can see, is if you _choose_ to use Java libraries within Clojure - and even that is just a matter of reading a library's documentation and applying the interop rules... Your snide remark about a build tool is not appropriate given how popular Leiningen is and how much work Phil and many others have put into it. Sean On Wed, Feb 15, 2012 at 7:38 PM, Armando Blancas <abm221...@gmail.com> wrote: >> Can you provide some more specific examples of what's missing? > > Surely you're joking, Mr. Hagelberg. > >> I don't know any Java and was able to manage pretty well. > > This is no time for modesty, lest the OP might feel his troubles > aren't even valid. Perhaps better to say that a rudimentary grasp of > Java (language, libraries, tools) can go a long way. Then one day... > we'll get a killer build tool or something. -- 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
