https://github.com/troy-west/cronut if you use integrant

You may also want to consider https://github.com/crinklywrappr/gooff

depending on your requirements Quartz (and perhaps the wrapper lib quartzite) might be the thing

chime is cool

and uses Java threaded worker pool thingy

You can only use case with compile-time literals. Java classes are not compile-time literals. I would avoid using java.util.Date at all if possible. If not, I would maybe look into converting java.util.Date into a LocalDateTime so that you can always just use DateTimeFormatter to format the date. If that's not an option for some reason, you might want to look into protocols (https://clojure.org/reference/protocols). That's what you'd generally use when you need to dispatch on the type of a thing.

Just to illustrate how case works:

(let [x 'java.time.LocalDateTime]
  (case x
    java.time.LocalDateTime "I'm a LocalDateTime"
    "I'm nothing."))
;;=> "I'm a LocalDateTime"

ok. thank you very much

There have been a few people attend ClojureBridge London events that helped start there career in software development, usually with little or no background in coding. Some went on to get Clojure roles, some continued Clojure as a side interest. My advice is to spend a part of your time understanding how you best learn something. What are the effective ways of retaining the things you are learning? There are many tools to help you learn Clojure (http://Exercism.org, http://Practical.li and many https://clojure.org/community/resources), so its a question of which help the most. There is more to learn than any one person can learn in a lifetime, so set small and obtainable goals. Identify some overall objectives you want to achieve (get a job doing x, or building a project to do x) and figure out things that get you closer to that. I dont beat yourself up if you get stuck or confused or projects fail. That's just part of life. If you get stuck, step away from the code and have a think. If you are still stuck, form a meaningful question and post it to the community (forming the question often helps answer your own question)

I suggest asking @UMA337M3P, though she isn’t always on Slack

depends on your background, it is certainly possible, resources are abundant and the community is welcoming

you have the upside of less preconceived ideas, languges like python or java or javascript may seem easier, but all languages are equally complicated in the end

I have to say I personally "fell into a ditch" last year when trying to learn clojure, and are now coming back to it after learning some of the other functional style languages, like F#

I'm also a self-learner so it's useful to learn languages like Tarzan, grasping concepts one at a time, climbing ever higher

each language provides easier way to some domain, and makes others harder

responded to @U01FK0L87DJ via PM

"forming the question often helps answer your own question" Universal step 1 for learning to code in any language: Buy a rubber duck or print a picture of one so you can talk to it.

Thanks for the answers everyone 🙂

is the plot jar clojure or java?

simple java class at this point,

(:import Plot.Plot) ;; works
(Plot.) ;; gives ClassNotFoundException

so the package is Plot, with an upper case?

I have no idea what that means, I don't use your ide

Yeah sorry just trying to give you an idea of how the java in the jar file is structured. So yes java eclipse IDE.

what happens in a repl if you try (Plot.Plot.) ?

dish the require and do (:import Plot Plot)

also, require is not appropriate here as there's no clojure ns to find and load

@U01KZDMJ411 I think you mean (:import Plot.Plot) or (:import [Plot Plot])

yes, correct

@U65G9MPCK for future reference, using normal conventions helps us understand what's going on / what's being attempted. Usually the package name isn't capitalized - only classes or things that are backed very straightforwardly by a class like records.

Doing

(:import [Plot Plot])

the import will invoke any static code on the class

for future reference, require tells the clojure compiler to find and load clojure code (which usually incidentally loads and/or defines classes), import tells Clojure that a class should be available by a shorter name in the current ns, import does not see aliases or mappings created by require, those exist in the world of clojure's compiler and its namespaces, which is parallel to and invisible to the world of classes

I mean you can write a class to look at namespaces and such, but that's not what you'll see outside clojure code

OK, sounds like require is not needed in this case.

right - it's only needed if you need clojure to compile clojure code

what I mean about import being sugar:

org.noisesmith.mp3=> (import ( ByteArrayInputStream))
java.io.ByteArrayInputStream
org.noisesmith.mp3=> (= ByteArrayInputStream java.io.ByteArrayInputStream)
true

OK so I managed to get something working with the following:

(:import [package_name ClassName])

(ClassName.)                 ;; instantiate ClassName in package_name
(.class_method (ClassName.)) ;; call class method

Thank you!