Most applications provide you configuration files that are data / text based. Whether it is toml, JSON, yaml or some other format, you are usually defining values for pre-determined keys and that’s all.

This makes sense for many applications, but involved applications have explored configurations that make use of scripting. For example, vim uses VimScript, neovim uses Lua, but vscode uses json (as far as I remember), and Helix (vim inspired editor) argues editor configurations must be data, not scripting, and uses toml.

many tiling window managers use various programming languages (Qtile uses python, xmonad uses Haskell, Awesome uses Lua) while others stick to data configuration (i3).

Do you think that scriptable configuration is over-engineered and brings weaknesses, or is it warranted and grants the user power in these big applications? What are the benefits of scriptable configurations?

  • it_a_me
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    1 year ago

    Turing Complete Configuration

    • more extensible
    • tend to be heavier
    • harder to provide detailed error messages
    • more difficult for new users

    Data Based Configuration

    • easier to use
    • easier to provide documentation
    • lighter to embed
    • more limited usecases