3 ms·

There really needs to be a JVM crash-course for clojure... I can understand the syntax well-enough, but I want to know what java libs i need/how i use them/etc.

There really needs to be a JVM crash-course for clojure... I can understand the syntax well-enough, but I want to know what java libs i need/how i use them/etc. ie. when I have to "leave clojure".

grayrest 13y ago
http://www.clojure-toolbox.com/ http://www.clojure-toolbox.com/ Clojure has been around long enough that people have wrappers around most of the interesting common use java libs. If you're looking for something domain specific then it's usually better to find which java libs cover the domain and work from there.
- DigitalJack 13y ago
  On top of that, direct java interop is not bad at all. Here is a talk on it: http://www.infoq.com/presentations/Clojure-Java-Interop http://www.infoq.com/presentations/Clojure-Java-Interop I confess I haven't watched that talk yet and only remembered hearing about it as I wrote this. But I imagine it is a good Launchpad.
  - andrewflnr 13y ago
    The point is, direct Java interop is useless, potentially worse, if you don't know anything about Java.
Skinney 13y ago
What do you mean? If you know Clojures syntax for Java interop, reading Java API's shouldn't be much of a problem. Searching for java howtos on how to use sockets and such should also give you a fair amount of results...
- mjburgess 13y ago
  Yes... but reading api documentation isnt a tutorial. I was asking for a tutorial for common java api stuff. If a tutorial goes through some common apis then you can get a feel for how to read the documentation through a clojure lens.
  - danneu 13y ago
    I've been productive with Clojure and Java-interop for over a year now despite never using Java before. Navigating the Java terrain is comical. Often, performing what I would consider a library's basic use-case involves the collaboration of multiple objects I never could've reverse-engineered from the API docs. Yet the library doesn't throw me a bone with any sort of `## Usage` overview. Fortunately, it seems nobody else knows how to do trivial things with Java (or libraries like Bouncy Castle) either, so I've found it reliable to lean on google queries to find the 1,000 questions that have already been asked and answered.
nonrecursive 13y ago
I plan on adding that to the book. In the mean time, I have a series on Java for Clojurists: http://www.flyingmachinestudios.com/programming/how-clojure-babies-are-made-the-java-cycle/ http://www.flyingmachinestudios.com/programming/how-clojure-...

There really needs to be a JVM crash-course for clojure... I can understand the syntax well-enough, but I want to know what java libs i need/how i use them/etc. ie. when I have to "leave clojure".

grayrest 13y ago

http://www.clojure-toolbox.com/ http://www.clojure-toolbox.com/ Clojure has been around long enough that people have wrappers around most of the interesting common use java libs. If you're looking for something domain specific then it's usually better to find which java libs cover the domain and work from there.

DigitalJack 13y ago
On top of that, direct java interop is not bad at all. Here is a talk on it: http://www.infoq.com/presentations/Clojure-Java-Interop http://www.infoq.com/presentations/Clojure-Java-Interop I confess I haven't watched that talk yet and only remembered hearing about it as I wrote this. But I imagine it is a good Launchpad.
- andrewflnr 13y ago
  The point is, direct Java interop is useless, potentially worse, if you don't know anything about Java.

Skinney 13y ago

What do you mean? If you know Clojures syntax for Java interop, reading Java API's shouldn't be much of a problem. Searching for java howtos on how to use sockets and such should also give you a fair amount of results...

mjburgess 13y ago
Yes... but reading api documentation isnt a tutorial. I was asking for a tutorial for common java api stuff. If a tutorial goes through some common apis then you can get a feel for how to read the documentation through a clojure lens.
- danneu 13y ago
  I've been productive with Clojure and Java-interop for over a year now despite never using Java before. Navigating the Java terrain is comical. Often, performing what I would consider a library's basic use-case involves the collaboration of multiple objects I never could've reverse-engineered from the API docs. Yet the library doesn't throw me a bone with any sort of `## Usage` overview. Fortunately, it seems nobody else knows how to do trivial things with Java (or libraries like Bouncy Castle) either, so I've found it reliable to lean on google queries to find the 1,000 questions that have already been asked and answered.

nonrecursive 13y ago

I plan on adding that to the book. In the mean time, I have a series on Java for Clojurists: http://www.flyingmachinestudios.com/programming/how-clojure-babies-are-made-the-java-cycle/ http://www.flyingmachinestudios.com/programming/how-clojure-...