I think ublue will win over nix in the longrun. Its layered approach to system design seems far more sane. Being able to take a base image and apply gaming patches over it then apply your own personal layer is such a great way for multiple people to build off the same base and not have to resign the wheel everytime.
NixOS is more fun for the user from a tinker point of view but Ublue is better for the distributors and the non tinker end users.
Looks like Bazzite is listed as an example derivative image. I’ve heard good things about that OS from newer Linux users’ perspectives. But is ublue something an individual user could personally customize, or more like something a development team or community project would build up from?
The landing page referencing layers and the Open Container Initiative, so is this more like a bootable container using overlay file system drivers?
One attraction I appreciate with Nix is the ability to overlay or overload default software options from base packages, without having to repeat/redefine everything else upstream, e.g. enabling Nvidia support for btop to visualize GPU utilization via a simple cuda flag. Replicating lazy-level-evaluation with something buildkit ARGs would be hectic, so do they have their own Dockerfile/Containerfile DSL?
I think ublue will win over nix in the longrun. Its layered approach to system design seems far more sane. Being able to take a base image and apply gaming patches over it then apply your own personal layer is such a great way for multiple people to build off the same base and not have to resign the wheel everytime.
NixOS is more fun for the user from a tinker point of view but Ublue is better for the distributors and the non tinker end users.
Oh, neat! Is this the project you’re referring to?
Looks like Bazzite is listed as an example derivative image. I’ve heard good things about that OS from newer Linux users’ perspectives. But is ublue something an individual user could personally customize, or more like something a development team or community project would build up from?
The landing page referencing layers and the Open Container Initiative, so is this more like a bootable container using overlay file system drivers?
One attraction I appreciate with Nix is the ability to overlay or overload default software options from base packages, without having to repeat/redefine everything else upstream, e.g. enabling Nvidia support for btop to visualize GPU utilization via a simple cuda flag. Replicating lazy-level-evaluation with something buildkit ARGs would be hectic, so do they have their own Dockerfile/Containerfile DSL?
Individuals can make there own custom images using blue build and templates for the starting image.
Oh, I see. Looks like one can use this method to create custom forks of downstream images such as Bazzite:
https://docs.bazzite.gg/Advanced/creating_custom_image/