Comment

Comment on Ditching Docker for Local Development

That seems like an argument for maintaining a frozen repo of packages, not against containers.

I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.

an argument for maintaining a frozen repo of packages

This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.

You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.

Nix verifies the external software is the same with checksums. It also does hermetic builds.

source

Sort:hotnew top

nickwitha_k@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago
Nix is indeed cool. I just see it as less practical than maintaining a toolchain for devs to use. Seems like reinventing the wheel, instead of airing-up the tires. I could well be absolutely wrong there - my experience is mainly enterprise software and not every process or tool there is used because it is the best one.

source
- huantian@fosstodon.org ⁨1⁩ ⁨year⁩ ago
  @nickwitha_k @uthredii I’d like to think a better analogy would be that nix is like using a 3D model of a wheel instead of a compass and a straightedge to make wheels hehe 🙃
  source
- uthredii@programming.dev ⁨1⁩ ⁨year⁩ ago
  
  I just see it as less practical than maintaining a toolchain for devs to use.
  
  There are definately some things preventing Nix adoption. What are the reasons you see it as less practical than the alternatives?
  
  What are alternative ways of maintaining a toolchain that achieves the same thing?
  
  source