3 ms·

Updating a constant versus a config parameter isn’t all that different if the build is fast. I do think modularity will remain important because it makes merge

Updating a constant versus a config parameter isn’t all that different if the build is fast. I do think modularity will remain important because it makes merge conflicts less likely, and a system with good modularity could look a lot like a plugin system, except that AI can likely deal with minor compatibility breaks if it’s clear what to do. It’s a similar argument to why Linux device drivers are in-tree. If there are API changes then the AI fixes the callers. Compile-time checks are good because it’s direct feedback to the AI.

hahahaa 2mo ago
But you now have a fork. Main branch gets refactored you have a merge conflict.
danbruc 2mo ago
Updating a constant versus a config parameter isn’t all that different if the build is fast. Not even remotely true except that in both cases you change a number in some text file. If you do it in source code, you have to get the source code, you have to identify the correct line[s], you need a build environment, you might have to reinstall the new version after the build. And on top of this you want to involve a language model in this. The difference in complexity, effort, and resource consumption is orders of magnitude. And we are not even considering that you will have to go through this for each future version to keep your modification included. This is an insane way to change a font size.
- 1718627440 2mo ago
  > you need a build environment If you have a self-sufficient OS, the build environment is already part of it. > you have to identify the correct line[s] Just run a full-text search on the old value.
  - danbruc 2mo ago
    Just run a full-text search on the old value. How often does 10 appear in the code base? And is the value you are looking for even 10 or does only the UI show 10 points but in code it is defined as 200 twip?
riknos314 2mo ago
> if the build is fast. ...and the build doesn't require any tools that aren't already on your machine, and there are no dependencies to download Many of the best tools I use are written in languages I don't program in and thus I don't want the build tools and package caches for those languages taking up space on my drive. I'll take the config file any day.

hahahaa 2mo ago

But you now have a fork. Main branch gets refactored you have a merge conflict.

danbruc 2mo ago

Updating a constant versus a config parameter isn’t all that different if the build is fast. Not even remotely true except that in both cases you change a number in some text file. If you do it in source code, you have to get the source code, you have to identify the correct line[s], you need a build environment, you might have to reinstall the new version after the build. And on top of this you want to involve a language model in this. The difference in complexity, effort, and resource consumption is orders of magnitude. And we are not even considering that you will have to go through this for each future version to keep your modification included. This is an insane way to change a font size.

1718627440 2mo ago
> you need a build environment If you have a self-sufficient OS, the build environment is already part of it. > you have to identify the correct line[s] Just run a full-text search on the old value.
- danbruc 2mo ago
  Just run a full-text search on the old value. How often does 10 appear in the code base? And is the value you are looking for even 10 or does only the UI show 10 points but in code it is defined as 200 twip?

riknos314 2mo ago

> if the build is fast. ...and the build doesn't require any tools that aren't already on your machine, and there are no dependencies to download Many of the best tools I use are written in languages I don't program in and thus I don't want the build tools and package caches for those languages taking up space on my drive. I'll take the config file any day.