Re:Zig cc: A drop-in replacement for GCC/Clang
by sjwright on Tuesday March 24, 2020 @07:56PM
(#22680389)
More broadly, containers solve the problem of reproducibility. No longer does software get to vomit crap all over your file system in ways that make reproducing a functioning environment frustrating and troublesome. They have the effect of side-stepping the dependencies problem, but that isn’t the core benefit.
[ Parent
| on HN ]
Re:Zig cc: A drop-in replacement for GCC/Clang
by senderista on Wednesday March 25, 2020 @01:12AM
(#22682104)
But the images themselves are not easily reproducible with standard build tooling.
Re:Zig cc: A drop-in replacement for GCC/Clang
by sjwright on Wednesday March 25, 2020 @02:55AM
(#22682530)
True—but that's far less of a problem, because it rarely occurs unexpectedly and under a time crunch.
Diffing two docker images to determine the differences between builds would be far less onerous than attempting to diff a new deployment against a long-lived production server.