This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-15
Channels
- # aws (25)
- # babashka (11)
- # beginners (24)
- # calva (18)
- # clj-kondo (6)
- # cljdoc (1)
- # clojure (48)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-uk (22)
- # clojuredesign-podcast (8)
- # clojurescript (9)
- # cursive (8)
- # dirac (6)
- # duct (19)
- # fulcro (17)
- # hoplon (29)
- # mount (3)
- # off-topic (24)
- # pathom (6)
- # re-frame (6)
- # shadow-cljs (5)
- # spacemacs (5)
- # sql (10)
- # tools-deps (7)
- # vim (2)
Hi there. Recently, some friends were trying to make a Clojure implementation for a different runtime... Then I remembered babaska and SCI. Would it be easier to star a new implementation using the parser / macro expander, etc of sci or bb, or am I waaaay off-track? Because starting a new implementation based on Clojure source code seems so much work...
@mauricio.szabo What runtime?
I think they were trying to migrate to dart. Some were trying to experiment with wasm or Python too
@mauricio.szabo Nowadays you can use sci from C / C++ / Rust, etc. https://github.com/borkdude/sci/blob/master/doc/libsci.md That's the closest thing I can think of of using sci from those kinds of envs
@borkdude well, to be honest, I was thinking on the reverse direction: to use sci / babaska to generate core (or bytecode) on other envs :)
I guess you could take sci as an example, but it's an interpreter, not a compiler. Maybe Clojure itself comes closer. "Just" generate machine code instead of JVM byte code 😛
is anyone else interested in file watcher functionality in bb? https://github.com/borkdude/babashka/issues/290#issuecomment-599193052