Clojurians Log v2
sci
Are there examples of using scittle with other JS libraries besides the bundled ones? (I'm thinking of D3 here but any examples of requiring an external JS lib from scittle will probably help me get started)
@afoltzm scittle currently doesn't support loading JS libraries in the ns form. The way this would work is just by loading d3 in a script tag and then using js/D3.whatever
@afoltzm Example:
<html>
<head>
<script src="" type="application/javascript"></script>
<script src=""></script>
<script type="application/x-scittle">
(-> (js/d3.selectAll "p") (.style "color" "blue"))
</script>
</head>
<body>
<p>This is a paragraph</p>
<p>This is another paragraph</p>
</body>
</html> 
Wanted to say that sci is exceptionally cool. I'm not aware of anything similar in other languages.
Also, I have a question. Does sci self host? In other words, can sci use sci to eval clojure code isolated from the outer sci layer? Just curious for now. It's like... We've got this Docker for Clojure, just without tons and tons of copied stuff, containers, images, versions, one might say bloat.
@teodorlu SCI cannot evaluate itself, but what is evaluated in a SCI context, created with (sci/init {...}), does not, or should not affect the host. E.g. creating vars in a context does not create vars in the Clojure runtime.
So I cannot use sci as a library from a Babashka script?
we could expose SCI itself in babashka, but so far I haven't done this
it is possible
Ok
I don't have a particular use case in mind, just curious
some people use SCI in the JVM to evaluate programs coming from web requests. SCI gives a form of isolation and you can control what vars are or are not allowed. One thing SCI doesn't do is protect you from long-running or never-ending loops, but both JVM and Node.js have lower level primitives for this
About the ANSI escape codes, are you looking for colored output?
There are two libs for this: • https://github.com/babashka/babashka/blob/master/doc/projects.md#clojure-term-colors • https://github.com/AvisoNovate/pretty
Yeah - deleted because I figured I could just experiment myself
Thanks, exactly what I was looking for 👍
In #nbb (SCI on Node.js) I've used something to kill for-ever running loops. E.g. if you type (range)in the REPL and then press ctrl-c, you're still in the REPL and the eval loop is killed.
On the JVM, would threads and .stop() be the way to achieve reliable interrupts?
in the JVM, CIDER uses .stop() on Threads to do the same. Unfortunately GraalVM doesn't support it, since they have decided not to implement the deprecated method
but if you're running SCI in a non-Graal JVM you could use .stop()
Ok, thanks 👍
as a note, cider uses .interrupt , wait, then .stop, https://github.com/nrepl/nrepl/blob/d875260afcecd6bfc2ff53a0be437cf2972250f4/src/clojure/nrepl/middleware/session.clj#L176
This allows tasks that do support interruption to property clean up.
Ahh, nice, thanks for the link. So... First try to kill "nicely", then permit 5 seconds for cleanup, then stop forcibly?
Yes, it seems like a reasonable balance which is good enough for trusted code in a dev environment. If you need true isolation, you probably want to run it in a separate process with appropriate sandboxing.
Right - and then you could just use OS interrupts instead?
https://clojurians.slack.com/archives/C015LCR9MHD/p1643925719149929 Does that mean that the answer to my original question is that • It's not really necessary to stack two sci interpreters for isolation because they can run "next to each other" • And the same isolation guarantees could be provided with an interface to sci/init and sci/eval from Babashka ? Just that it hasn't been needed so far?
yes
I guess running sci inside sci inside sci..... Is going to perform poorly at some point 😄
Ok, that makes sense 👍
GraalVM has a JVM bytecode Truffle interpreter which can run inside of itself
but unfortunately loading Clojure in that thing takes 30 seconds or so
Defeating babashka's primary selling point :)
Exactly. I've tried initializing the clojure loading in a static initializer with espresso (the name of the bytecode interpreter) but that didn't work out