3 ms·
No it is usually not the case. There is a real difference between declarative and imperative approach to configuration and such decisions can be traced in many
by haddr 7y ago
No it is usually not the case.
There is a real difference between declarative and imperative approach to configuration and such decisions can be traced in many projects.
Simplifying things: declarative configuration is usually the best approach if you manage to capture most of your component behaviour in some relatively simple language with limited expressivity.
Imperative is where you start mixing some code in. This is usually because of big amount of corner cases and where flexibility is a must. This is seen quite often in build tools: it’s hard to just configure everything, some projects need to be built using really custom pipelines.