User-directed updates

Tags
Nix
Updated at
Jul 20, 2024 4:14 PM
Published at

The Crowdstrike BSoD outage is a good example of something that happens all the time. The user decides to use the software, to get something done. The software decides to run an update instead. The user now has to fix, find workarounds or get used to the user interface in the new version.

The same issue appears in Dockerfile and other developer environments. The developer wants to get something done, something changed, and they are now fixing their environment.

What if the user was in control? What if they could decide when to update their software? And rollback to a previous version if things start breaking?

In order to make that a reality, you would have to describe

This is only

This is something we take for granted when using Nix.

This is what Nix has to offer.

That’s Nix.