@harsjoshi1614 To augment the great resources above, here's hands-on material that drills the REPL-oriented habit (among other things important for newcomers): https://github.com/inclojure-org/clojure-by-example (I'm the primary author of the workshop. We teach it at IN/Clojure every year.)

Has anyone looked at the Learn Reagent, Learn Re-frame, and Learn Reitit courses? Are they worth recommending to someone who wants to jump in quickly?

is there a way to check using clojure.spec if an entity is a function?

I'm not sure what you mean by entity but there is the ifn? predicate

is it possible to add a path to the clj repl invocation without using -Sdeps? i can say clj -Sdeps {:example {:extra-paths ["test"]}} -M:example, but that’s much more verbose than something like clj -Spaths ["test"] or similar

to be clear, i want to add to the existing :paths vector that already exists in the deps.edn, not replace

the reason i ask is because i have an alias :test {:extra-deps {lambdaisland/kaocha {:mvn/version "1.0.861"}} :extra-paths ["test"] :main-opts ["-m" "kaocha.runner"]} , and the :main-opts is run when i use clj -M:test, when what i’m looking for is to just pull in the deps and path

A quick clarification on specs and instrumentation. Am I correct if I'm under the assumption that instrumentation means that all used functions get their inputs validated and no other checks are generated?

if I understand you correctly, yes, but there can be surprises, eg. an arg that is a function can get called with generated args to verify it has the expected type

a-huh.. hence the problems with higher-order-functions

Hi all, does clojure.tools.cli support not having short flags? I couldn't find any reference of anyone doing something like that

(def cli-opts
  [["-d", "--boot-disk-size SIZE", "Size of boot disk (format: 150GB)"]
   ["-b", "--boot-disk-type TYPE", "Type of disk (eg. pd-ssd)"]
   ["-n", "--name NAME", "Name of instance"]
   ["-t", "--machine-type TYPE", "Type of instance"]
   ["-i", "--image-family IMAGE", "Name of OS image to boot"]
   ["-z", "--zone ZONE", "Region to boot instance"]
   ["-x", "--no-address", "No address?"]
   ["-h", "--help", "Display help"]])

> Option specifications are a sequence of vectors with the following format: > [short-opt long-opt-with-required-description description > :property value] > The first three string parameters in an option spec are positional and > optional, and may be nil in order to specify a later parameter.

sounds like you must include the position but can make it nil

ah! great thank you @dpsutton

Is it common to assign a global binding with def when performing interactive / repl development, even if it's intended to be assigned with a defonce? Is this the preferred route during iteration to avoid restarting the jvm?

the principled version is something like component / integrant / mount

but using def to bind in the repl is a normal thing yes

i do lots of (comment (def foo ...)) all the time

I’m trying to work with Playwright in CLojure and they have a Java line that looks like this

Browser browser = chromium.launch(new BrowserType.LaunchOptions()  .setIgnoreDefaultArgs(Arrays.asList("--mute-audio")));