3 ms·
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
by kccqzy 11mo ago
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.
- nish__ 11mo agolol man... If your "config" is Turing-complete, that's a code change. Full stop. Bro's just lazy.
- kccqzy 11mo agoYeah 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.