On Wed, Mar 23, 2011 at 8:11 AM, ultranewb <pineapple.l...@yahoo.com> wrote: > I'll be damned - this worked. Really, there needs to be some > prominent, easily-accessible guides for just dumb, ultra-basic stuff > like this. I'm talking guides that assume the user has no knowledge > of anything except "programming" and "editing" (I mean, I don't even > know what the heck a "jar" file is). And these guides need to be > linked right at the front page of the Clojure site. > > Anyway, thanks.
If it helps, I feel your pain. I bought books on Clojure, read everything I could, and it still took me 8 months of on and off again trials till I finally understood how it worked. Part of the issue is Java, imo. The whole java class path thing is very annoying. I think I got python up and running on my box in a matter of minutes. C# has such a nice IDE that it's super-simple to start programming in that. Even Ruby has excellent instructions on how to get started. Clojure on the other hand has it's own way of doing things, and when it can't resolve something it looks to Java, and from there Java tries to find libs and symbols and if it can't, it just blows up with some cryptic Java exception. Yeah...that's the down-side of working with a language that sits on the JVM. </rant> Don't get me wrong, I love Clojure, but the learning curve can be steep. Timothy -- 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
