Remix.run Logo
▲ paulvnickerson 2 hours ago

They didn't have to go with NixOS...

▲whazor an hour ago | parent | next [-]

They previously used openSUSE and then Fedora. But both have companies behind them, where-as NixOS does not. And with NixOS they are more sovereign.

▲orbital-decay 20 minutes ago | parent | next [-]

NixOS (or rather nixpkgs) in its current state heavily depends on GitHub/Microsoft at the very least, and switching to anything else is non-trivial.

▲andsoitis an hour ago | parent | prev [-]

> They previously used openSUSE and then Fedora.

Why did those not work out? Why do they think things will be different with NixOS?

▲Ilaurens 37 minutes ago | parent | next [-]

Fedora is connected to Red Hat which is a US company, which is exactly the dependence that is undesired

▲geek_at an hour ago | parent | prev [-]

Because it was suse and fedora

▲vishalontheline an hour ago | parent | prev | next [-]

Somewhat related: https://www.thestack.technology/nixos-atomic-os-france-sover...

▲thrance an hour ago | parent | prev | next [-]

I think it makes sense? You probably get an easier time reproducing a config on thousands of devices using NixOS?

▲lurkerforawhile an hour ago | parent | next [-]

it makes so much sense. a small team of experts maintaining a rock-solid base configuration providing the essentials, which can then be built on top of for agency/department or even personal specifics - all declarative, immutable, cachable, testable. I can't think of a better tool for the job.

▲viraptor 19 minutes ago | parent | next [-]

As a downside, any change to software, version updates, keeping things secure now depends on the team is experts. Most are easy, some are hard (e.g. new software now requires a new Swift version - one person motivated enough to do that project has been pushing it for months), some are annoying (patch to libc means you're re-downloading your whole system).

As a positive thing, maybe at least nixos will get a serious security pipeline rather than the current best-effort community approach.

▲tosti 17 minutes ago | parent [-]

Well that was the whole problem to begin with! A lack of experts. Hence they went with IBM and MicroSlop. These guys are late.

▲tosti 18 minutes ago | parent | prev [-]

buildroot

▲viraptor an hour ago | parent | prev [-]

Golden image deployments and netboot have been around for ages. If you want an unified system and control the infrastructure, it doesn't really matter which system you use.

I'm not sure why they chose nix. But it does make it easier to carry local patches than a lot of other systems. I hope they succeed.

▲tosti 20 minutes ago | parent [-]

The one that makes it trivial to carry over local patches is Gentoo. I carry a set of patches to every new computer and update them whenever neccesary. No overlay yet :P

▲AmazingTurtle an hour ago | parent | prev [-]

Had to be a team of circle jerk external advisories that want to become rich by inflating the effort here

▲tfrancisl 11 minutes ago | parent | next [-]

I dont think Determinate Systems was involved, despite their proximity to the Netherlands (Eelco being Dutch). They work with American arms manufacturers, so I suspect that may play a role.

▲pessimizer 14 minutes ago | parent | prev [-]

This is my fear.