News for hackers. Stuff that matters.
Re:The Dhall Configuration Language by na85 on Thursday July 14, 2022 @08:04PM (#32102889)
Apparently I'm in the minority that feels config languages should be little more than namespaces and key-value storage and should not be programmable.

I would not want to use a bash script as a config file, for example.

Re:The Dhall Configuration Language by Ixiaus on Thursday July 14, 2022 @08:13PM (#32102958)
I too don't want to or would use a bash script as a config file. That's the point of dhall: you get good static types and it's not turing complete, so you get a lot of the safety and code reusability tools without the pitfalls of a general purpose programming language.

And, have you ever worked with giant configs in json or yaml? It becomes incredibly painful to manage.

Re:The Dhall Configuration Language by na85 on Thursday July 14, 2022 @10:05PM (#32103809)
I prefer to use multiple, smaller config files to keep them manageable.
Re:The Dhall Configuration Language by benlivengood on Thursday July 14, 2022 @10:16PM (#32103887)
My biggest pain when doing this is: set up an environment configuration. Then set up a test or stage environment that matches it. Then modify the environment over the next few years keeping the stage and production environment configs in sync so that testing and validation are useful (the stage configuration actually matches production so that success or failure in staging predicts the same in production) before going to production.

Even something as simple as variable substitution becomes very useful in these cases so that configuration can be a single file and substitution delivers the staging or production config. Functions and operators allow more complicated configurations to remain DRY. Checks prevent the stage servers from using the production database connection string, etc.

Re:The Dhall Configuration Language by jhhh on Thursday July 14, 2022 @10:45PM (#32104071)
People tend to evaluate these things based on what cool and neat things they can do it with. Not whether telling people they need to learn Haskell before they can update what would've been a 30 line configuration file on the project they just joined is a good use of peoples' time.
Re:The Dhall Configuration Language by astrange on Thursday July 14, 2022 @09:53PM (#32103726)
I think more programming power is useful in the service of stopping bugs; for instance, you could have a language where the part that "does stuff" isn't Turing complete, but the part that "stops incorrect stuff from happening" (the type system) is.