I couldn't find a book that exactly matches Clojure. Still, I prioritize Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F# by Scott Wlaschin. However, many concepts, such as algebraic data types, wrapper types, and monads, may need to be adapted or even ignored.
I haven't applied clean architecture with Clojure, but I'm working on a Python codebase that uses dependency injection intensively. It works, but I personally feel the pain every time I create a mock.
Although the clean architecture book mentioned vertical-slice architecture and added a new chapter about packaging by technical layers versus by features, clean practitioners seem to prefer packaging by layers, which should be approached with caution. I don't remember if the book mentions pushing I/O to the edges, or the imperative shell pattern, which would allow pure functions to cover more logic instead of having a service layer that interleaves I/O and logic.
I couldn't find a book that exactly matches Clojure. Still, I prioritize Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F# by Scott Wlaschin. However, many concepts, such as algebraic data types, wrapper types, and monads, may need to be adapted or even ignored.
I haven't applied clean architecture with Clojure, but I'm working on a Python codebase that uses dependency injection intensively. It works, but I personally feel the pain every time I create a mock.
Although the clean architecture book mentioned vertical-slice architecture and added a new chapter about packaging by technical layers versus by features, clean practitioners seem to prefer packaging by layers, which should be approached with caution. I don't remember if the book mentions pushing I/O to the edges, or the imperative shell pattern, which would allow pure functions to cover more logic instead of having a service layer that interleaves I/O and logic.
The hard part for me was dynamic scope, which I found it was explained nicely in The Common Lisp Condition System: Beyond Exception Handling with Control Flow Mechanisms. Since then I have begun to feel that dynamic scope in Bash is a feature, not limitation.
Cachy, Endeavour, Garuda, etc should be fine.
Since you are a coder, I suppose you using CLI should be fine. However, there are many other alternatives, which is fast and even based on Arch Linux.
In the 90s, QBasic (IDE) and Edit didn't work on Slackware. So, I tried Pico, Vim, and Emacs. Now, I still use Emacs.
Do you mean moving Pydantic models as arguments of other function?
With some certain distros, it is easy.
Thank you for providing rationale.
Thank you.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063034
With CachyOS and Mint, it is very easy.
Remark: I disabled secure boot.
No, I haven't.
I usually confuse between data-driven and data-oriented. So data-driven development is not the same as data-oriented programming, is it?
I'm not going to use this name, but it is the most accurate one.
It means I probably won't fix bugs.
I hosted it on Codeberg https://codeberg.org/veer66/flatswitch/commit/c9f14155b3e6e6a9d0ca92443d8d827a80fd73f5
I'm not sure what version control implies in this case. Still, we can downgrade version of packages that we installed by Flatpak.
I love this name.