zlacker

[parent] [thread] 2 comments
1. kccqzy+(OP)[view] [source] 2025-12-05 18:50:34
Config updates are not so clear cut from code changes.

Once I worked with a team in the anti-abuse space where the policy is that code deployments must happen over 5 days and config updates can take a few minutes. Then an engineer on the team argued that deploying new Python code doesn’t count as a code change because the CPython interpreter did not change; it didn’t even restart. And indeed given how dynamic Python is, it is totally possible to import new Python modules that did not exist when the interpreter process is launched.

replies(1): >>nish__+z72
2. nish__+z72[view] [source] 2025-12-06 14:40:24
>>kccqzy+(OP)
lol man... If your "config" is Turing-complete, that's a code change. Full stop. Bro's just lazy.
replies(1): >>kccqzy+Py2
◧◩
3. kccqzy+Py2[view] [source] [discussion] 2025-12-06 18:21:14
>>nish__+z72
Yeah sure. Now tell the people who are designing config languages to make them both powerful and non-Turing-complete. You see, it is a very hard problem for a powerful language to be non-Turing-complete.
[go to top]