I think the pipeline paradigm you speak of is powerful, and some of the clarity issues you claim can be improved through clear and consistent use of keyword destructuring in function signatures. Also by using function naming conventions ('add-service-handle' etc.) and grouping functions in threading forms which have additive dependencies, can also address these frustrations.
Comments
I think the pipeline paradigm you speak of is powerful, and some of the clarity issues you claim can be improved through clear and consistent use of keyword destructuring in function signatures. Also by using function naming conventions ('add-service-handle' etc.) and grouping functions in threading forms which have additive dependencies, can also address these frustrations.
this is the new standard in hyperscale. Even Microsoft is doing Medallion architecture in Fabric.
if you are going to be modifying the same data with a sequence of functions, you got to write that down somewhere so new people get it.
Lisp is great at processing lists in such a manner.