2 ms·

I think the problem is less determinism than predictability. Hashing algorithms are deterministic. Will people start .gitignore-ing their src directories and o

• dist-epoch 7mo ago
  https://github.com/dbreunig/whenwords https://github.com/dbreunig/whenwords
• ModernMech 7mo ago
  This article [1] would argue ”no”, because then you would be ridding yourself of a “repository of determinism”, which the prompts cannot replace. You can build a system with non-deterministic properties but you need some sort of deterministic foundation to build working, usable systems. Non determinism from top to bottom is building on quicksand in a swamp. [1] https://www.oreilly.com/radar/can-language-models-replace-compilers/ https://www.oreilly.com/radar/can-language-models-replace-co...
  • zephen 7mo ago
    There are multiple reasons why binary repository managers like Artifactory exist. And, arguably, the primary reason that perforce is still popular in some domains is that it works well with both large and opaque objects. Once you've decided to version your src directory, whether a priori or because once bitten, twice shy, the next question is: Is git the correct version control for this? Or are all the changes so large that git's advantages in merging and manually diffing things become irrelevant?