they have people watching them, a lot sometimes. I think they should at least share actual information on that matter. Not some twisted version or vision.
Also reading back the whole thing with the anti-cheat stuff is a load of bollocks, its like every game devs worst nightmare and every game publishers dream... Tbh the way to look at most anti-cheat now is basically Crowdstrike for games
tbf, I not-so-low-key hate nix. The language, the giant ball of mud that is nixpkgs, the horrible documentation, the incredible degree of over-engineering for simple things, the ridiculous drama that seems to infect most of the community. But I keep coming back like an abusive relationship, because nothing else gives me the capability to go from a single set of consistent declarative config files in source control to a set of fully configured machines. I think a tool sitting atop a uBlue-like atomic distribution could give me the things I want, eventually. So I keep watching these spaces and waiting.
That gets me about half way there. The problem is that the lack of tooling within the container building itself; your tools are the ad-hoc collection of things like COPYing manually maintained config and systemd unit files, having to use things like sed to do inplace edits to add specific configuration to a machine to the default files, etc. I actually inflicted myself with the pain of nix moving from a container-based approach because the tooling for making the container itself was not replicable enough.
Because once you've drunk the nix koolaid enough to do that, largely you might as well just use NixOS and be done with it. It gives you more or less all the same benefits of an atomic distro at that point, including the same generational update capabilities, controlled updates, and so on. The only real advantage would be layering over the fantastic work people like you guys have done getting a stable combination of kernels and appropriate configuration for drivers and system software like power and sound subsystems. Looking at my nixos config right now, about a quarter of it setting up things like pipewire, lactd, tlp and thermald, kernel param and sysctls, etc, much of it cribbed from looking at configs from Bazzite and reconciling them with other people's nixos gaming configs for how to set such things using nix.
Of the remainder of my config, about a quarter is managing secrets using SOPS (host keys, ssh auth keys, tailscale) and user permissions, a quarter common sysadmin things like disk partitioning, hostnames, timezones, NFS mounts, nix's own settings for the store and updates, and so forth. The rest is installing and configuring all my personal software packages.
I would gladly farm out all the first part to Bazzite if I had a non-Nix way to concisely and consistently do the second part. For years I did the route of hand maintained shell scripts that used various package managers directly in combo with tools like stow or chez moi. I've used Ansible, chef, puppet and similar in the past.
J
P
K
K
S
R
M
Q
R
