Host language is rarely ever declarative. Declarative languages are often necessary because they don’t leave any escape hatches that tempt you into writing incorrect code. Build system dependency graphs one common example. It’s also needed to pass data between different systems without recompiling and to constrain the usage boundaries, especially around security.
Imagine how absurd it would be if mongodb queries were written in the host language C++ instead of json.
For in-house stuff agree. There is no point to make excessive config layers if only developers will touch it anyway.
> For in-house stuff agree. There is no point to make excessive config layers if only developers will touch it anyway.
Yeah, I'm specifically talking about in-house DSLs or those that are only used by/from specific users. That doesn't have to be developers, but they should be using the host language as well - and in that case, an imperative host language can still make it able to use a declarative DSL. (in the most basic way for instance: generate a datastructure that essentially describes a json/yaml or whatever)
For non-inhouse DSL, I agree that it is usually worthwhile to make them standalone.
Imagine how absurd it would be if mongodb queries were written in the host language C++ instead of json.
For in-house stuff agree. There is no point to make excessive config layers if only developers will touch it anyway.