News for hackers. Stuff that matters.
Re:Typed Config Languages by jandrese on Friday January 21, 2022 @04:05PM (#30029992)
In the past it was fairly common to write configuration files in TCL and just running the script to parse them.

This was generally considered to be a mistake. It opens up a huge threat surface for your program and few people ended up using the more advanced capabilities it created. If your config format supports simple globbing that covers the 95% use case for otherwise needing a turing compete language for your configuration files.

Re:Typed Config Languages by kaba0 on Friday January 21, 2022 @05:03PM (#30030555)
That’s why I think Dhall is really interesting, it being purposefully not Turing-complete, yet still very flexible.
Re:Typed Config Languages by AaronFriel on Friday January 21, 2022 @04:34PM (#30030292)
I think that speaks to having that flexibility when needed. The other 5% of use cases are significant too.
Re:Typed Config Languages by jandrese on Friday January 21, 2022 @04:53PM (#30030474)
The other 5% is generally solved by people who write scripts to generate the config files. It's not like they're up a creek.
Re:Typed Config Languages by blacksqr on Friday January 21, 2022 @05:38PM (#30030866)
> This was generally considered to be a mistake.

Pity. Tcl allows you to create safe interpreters within which you can disable any commands you want in order to have a trustworthy environment for running configuration scripts.

Tcl itself uses them to build its internal list of available package modules.