7 ms·
IMO screw that. It's maybe a good way to build software in exactly one environment for exactly one environment, deployment to a corporate server fleet. Conside
by ahartmetz 7d ago
IMO screw that. It's maybe a good way to build software in exactly one environment for exactly one environment, deployment to a corporate server fleet.
Consider a Linux desktop distro: if every little binary (out of order of magnitude 1000) acted like the center of the universe with gigabytes of build environment and "opinions" galore instead of portability, builds would take much more resources than they already do and parts wouldn't necessarily work together.
- forrestthewoods 6d agoDeduping files is easy.
- ahartmetz 5d agoIt's also useless if every tool lives in its own copy of the universe - there'd be little to no identical files. It also won't work for version control databases, assuming use of a distributed VCS.
- forrestthewoods 5d agoYes it would require a global blob store across reps. That seems like a good design choice. I don’t know what you mean by “ won't work for version control databases, assuming use of a distributed VCS.”
- ahartmetz 5d agoThe .git directory does not contain plain files, so the same files may look different in different .git directories. But yeah, you could make it work if you designed for it.
- forrestthewoods 5d agoYeah Git is super mediocre. But the hypothesis is that you could build something that doesn’t suck!