| > It's pretty cool that this can host other distros, but is that the only advantage over NixOS? The ability to transparently get features from other distros is Bedrock Linux's defining characteristic. It's not trying to do anything more than that. Ideally the contrast wouldn't be Bedrock _or_ NixOS, but rather NixOS alone or Bedrock with NixOS. Bedrock's goal of getting features from other distros includes distros like NixOS. Sadly, there's still R&D work to be done there: while Bedrock supports a large number of distros, NixOS isn't yet one of them. > I don't know if I would enjoy crossing distro boundaries constantly just for a small handful of desired packages, and I'm not sure what other use cases this might have. I think trying to find use cases other than getting features from multiple distros is driving you in the wrong direction for modelling Bedrock. Most Linux users - quite likely including yourself - are happy with what one distro provides them. Others, however, find it limiting. Bedrock targets the latter group. Try thinking of scenarios where a user has competing pressures for different distros: - A user may require RHEL for work, but miss the large package selection offered by Debian. - A user may like Void Linux's init, but miss Arch's AUR. - A user may like Gentoo's ability to customize packages, but only want to compile about half the system. > Does anybody have experience deploying Bedrock in production? What are some pros and cons? You might be looking for these FAQ entries [0] [1]. [0] https://bedrocklinux.org/faq.html#why-use-bedrock
[1] https://bedrocklinux.org/faq.html#why-not-use-bedrock |