This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-03
Channels
- # aleph (2)
- # announcements (13)
- # babashka (7)
- # beginners (36)
- # calva (26)
- # cider (11)
- # circleci (13)
- # clj-kondo (15)
- # clojure (105)
- # clojure-europe (79)
- # clojure-nl (3)
- # clojure-uk (6)
- # clojurescript (17)
- # conjure (4)
- # core-logic (2)
- # cursive (10)
- # data-science (5)
- # datalevin (11)
- # datalog (14)
- # eastwood (6)
- # emacs (2)
- # figwheel-main (1)
- # fulcro (34)
- # google-cloud (1)
- # graphql (3)
- # introduce-yourself (7)
- # jobs (1)
- # leiningen (17)
- # lsp (46)
- # malli (2)
- # minecraft (3)
- # missionary (19)
- # off-topic (31)
- # other-languages (49)
- # polylith (2)
- # portal (5)
- # practicalli (1)
- # quil (77)
- # releases (1)
- # remote-jobs (1)
Do I understand it right that the notion libraries are frozen code
relates to the development process? Is the polylith-monorepo not frozen
because one can change code more easily in the same repo?
Yes, you are right. My view on this topic is that your code in the workspace is the code that you can dynamically work on the REPL and change through your IDE. Libraries are frozen during this process, even though you can update libraries with tools.deps
via add-libs
, the code in the libraries cannot be changed directly. You’ll need to load the new library version to get the updated code, hence they are considered frozen.
👍 2