This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-18
Channels
- # announcements (5)
- # aws (4)
- # babashka (30)
- # beginners (90)
- # calva (31)
- # clj-on-windows (16)
- # clojure (110)
- # clojure-dev (10)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (20)
- # clojure-spec (25)
- # clojure-uk (15)
- # clojured (2)
- # clojurescript (12)
- # code-reviews (2)
- # community-development (3)
- # conjure (14)
- # datomic (15)
- # defnpodcast (2)
- # events (1)
- # fulcro (17)
- # graalvm (8)
- # gratitude (1)
- # introduce-yourself (2)
- # jobs-discuss (7)
- # kaocha (6)
- # lsp (9)
- # luminus (5)
- # nextjournal (7)
- # observability (9)
- # off-topic (71)
- # portal (5)
- # practicalli (1)
- # rdf (21)
- # re-frame (15)
- # releases (1)
- # shadow-cljs (24)
- # testing (7)
- # tools-build (13)
- # tools-deps (14)
- # xtdb (7)
@borkdude sure! I'm working on a programmable dev platform (https://polytope.com/ — needs to be updated but hopefully you get the idea). You can think of it as a bare-bones but very extensible mix of, say, Replit, Heroku, and CircleCi. You build and run jobs (for CI/ML/running services/whatever) using Clojure/JS/Python, and can also package parts of jobs into composable "modules" that others can use to build their own jobs. It currently runs as a cloud service, and I'm using native-image to build a standalone version for on-premise use.
Thanks! I'm using SCI for running Clojure code in jobs btw — thanks for creating it 😉
Otherwise I'd be stuck with the languages provided by GraalVM
@U15RYEQPJ Would you mind sharing something here about your SCI usage? https://github.com/babashka/sci/discussions/662
Sure, will do 🙂