> "CLI args are usually passed around explicitly" -- I think this is a pro, not a con. Sure; I never said it's a con. They have different characteristics, and

> "CLI args are usually passed around explicitly" -- I think this is a pro, not a con. Sure; I never said it's a con. They have different characteristics, and are both useful in certain situations :) > I think the correct term for "things the caller knows better than the implementor" are parameters. True; that's also the name Racket gives to dynamically-scoped variables https://docs.racket-lang.org/guide/parameterize.html https://docs.racket-lang.org/guide/parameterize.html In fact, Racket uses a parameter (dynamically-scoped variable) to store the environment. This is actually slightly annoying, since the parameter is one big hashmap of all the env vars; but I usually want to override them individually. One of my Racket projects actually defines a helper function to override individual env vars makes a copies all the other environment ( made a are contained in a parameterhttps://github.com/Warbo/theory-exploration-benchmarks/blob/2862edcc3584b511dc54a72ecd1a5fc12cc71ab3/scripts/lib/impure.rkt#L24 https://github.com/Warbo/theory-exploration-benchmarks/blob/...