This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-20
Channels
- # announcements (1)
- # asami (6)
- # babashka (21)
- # beginners (19)
- # calva (44)
- # circleci (3)
- # clj-http (3)
- # clj-kondo (44)
- # clojure (24)
- # clojure-australia (1)
- # clojure-czech (1)
- # clojure-europe (50)
- # clojure-france (5)
- # clojure-germany (1)
- # clojure-nl (2)
- # clojure-spec (8)
- # clojure-uk (8)
- # clojurescript (161)
- # datomic (4)
- # fulcro (7)
- # graalvm (8)
- # heroku (4)
- # lambdaisland (4)
- # lein-figwheel (5)
- # lsp (48)
- # malli (21)
- # meander (15)
- # off-topic (35)
- # polylith (2)
- # re-frame (21)
- # react (22)
- # reagent (13)
- # reitit (6)
- # remote-jobs (1)
- # reveal (3)
- # ring (3)
- # shadow-cljs (37)
- # testing (2)
- # tools-deps (10)
- # vim (18)
- # vrac (1)
- # xtdb (17)
This video seems somewhat related to what Polylith brings to the table. Rafal is very good at formulating both problems and solutions. https://youtu.be/7HpI7d3-hpo
Yes, he explains the problem really well. There are differences in the two approaches. They cover both frontend and backend, while Polylith only covers the backend at the moment. They can swap out functionality at runtime, while Polylith decides what to include at compile time. To me, Polylith looks simpler and more formalised, but less flexible at runtime. This was really interesting to watch, and I agree that they are related, so thanks for the link @U0ETXRFEW!