[bsnnkv]

> However don't you fear to get to a kind of CMake state with a "old" and "new" way to get things done being both available for the sake of backwards compatibility becoming quite a mess ?

Right now there is support for dynamic configuration through commands executed through a script at startup (like bspwmrc etc), and declarative configuration through a static file which can be hot-reloaded.

Basically all new features and documentation are declarative-first, and there is a command that can generate a declarative configuration file from a running instance configured using a dynamic configuration script.

So if you're new to the project, you probably don't even know that the older configuration method is a thing, and if you come back to the project with a very old dynamic config script after a long time, everything you remember still just works, and you're just a command away from migrating to the format that everyone else is now using.

That being said, there is definitely a whole bunch of code that I would love to get rid of some day :)