This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-03
Channels
- # aleph (1)
- # announcements (3)
- # aws (36)
- # babashka (35)
- # beginners (25)
- # cider (14)
- # clj-kondo (3)
- # clojure (154)
- # clojure-europe (8)
- # clojure-italy (2)
- # clojure-nl (5)
- # clojure-serbia (1)
- # clojure-uk (133)
- # clojurescript (36)
- # cursive (15)
- # data-science (7)
- # datomic (16)
- # fulcro (34)
- # immutant (9)
- # jackdaw (5)
- # jobs (1)
- # leiningen (39)
- # off-topic (25)
- # pathom (42)
- # planck (13)
- # play-clj (1)
- # re-frame (18)
- # reagent (6)
- # reitit (3)
- # remote-jobs (1)
- # ring-swagger (16)
- # shadow-cljs (67)
- # sql (22)
- # testing (1)
- # uncomplicate (2)
- # vim (21)
- # vscode (6)
@chris441 thanks a lot for libpython-clj. I have more fun coding python in Clojure than using raw python xD
My colleagues will hate me.
We should still find a way to have concurrency and then it will be a killer.
Clojure's concurrency/parallelism primitives are superior to Python's. So the best route is the break your problem up such that you can use both languages where they are strongest. Another option will be to get libpython-clj working with graalvm and launch several lightweight processes. I think those are going to be the only options for some time. This has been discussed ad nauseum in an early issue.
I think GraalVM seems interesting. But it would python from Graal right?