This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-25
Channels
- # babashka (7)
- # beginners (116)
- # cljfx (2)
- # clojure-europe (6)
- # clojure-korea (4)
- # clojure-nl (1)
- # clojure-uk (1)
- # conjure (3)
- # data-science (3)
- # datahike (4)
- # events (4)
- # hyperfiddle (3)
- # missionary (11)
- # off-topic (134)
- # pedestal (1)
- # reitit (4)
- # releases (2)
- # shadow-cljs (12)
- # sql (3)
- # squint (1)
- # yamlscript (12)
I'm trying to understand a difference I'm seeing between running clj
and running bb
on the command line. I have this simple file, repl.clj
:
(require '[clojure.core.server :as server])
(server/start-server
{:name "repl"
:port 1666
:accept 'clojure.core.server/repl
:server-daemon false})
If I run clj repl.clj
, a socket repl server starts up, and I can successfully run echo "(+ 2 2)" | nc localhost 1666
to eval a form.
If I run bb repl.clj
, the program exits immediately, and no server starts up. Is this expected? Do I need to do something else with bb?
For context, I'm manually trying to setup a bb
socket repl so I can customize some things about it (like the prompt), as I'm experimenting with sending forms from the Helix editor using nc
.in clj, the JVM Clojure process waits for any non-daemon threads to finish I believe
Oh nice, thank you so much, I see that in the book now. And thanks for explaining the difference, is not-waiting for non-daemon threads just a GraalVM thing?