3 ms·
A cautionary tale in how not to implement configuration files. Don't make them a Turing-complete programming language.
by rwmj 14y ago
A cautionary tale in how not to implement configuration files. Don't make them a Turing-complete programming language.
- baq 14y agosimple solution: don't even try think of them as configuration files. vim and emacs have the same issue and you don't hear many complaints.
- rwmj 14y agoWell that's not so convenient in virt-v2v, where we have to parse grub2 configuration files to work out what they mean, what kernel is actually going to boot by default, what options it'll be booted with etc. In fact the current approach we take is to ignore grub2 configuration. Very tellingly, all the important distributions ignore the files too. They generate the files from ordinary static configuration files stored elsewhere (in different places for each distro, naturally). So we parse those files instead.
- mhurron 14y agoBut programming in your programming is so awesome (Yo dawg). Just look at how amazing Sendmail is.