Pyeah that is also true
Jlike all of the bazzite vids mostly have the same negatives.
J"can't play anticheat games" and a bunch of stuff that's not our problem. Being invisible is much nicer than being a problem.
Kbeauty of a gaming distro
Knobody's overthinking "yeah but how are the splines articulated?"
Kand instead are asking "does it run crysis?"
Pthis is stupid because you can't play anticheat games on steamos also
Jthey're arguing over "should we call the splines immutable?"
PI mean
Psome anticheat games
Jright, exactly
Jomg
Jhere comes the "nixos like features"
Pcringe...
Pdeclerative config is not nix invention...
Ppeople...
J
KAlso I love Linux people mentioning random distros with 3 users
Jwe have at least 3, wo we're good
Pyay!
Jvanilla's wallpaper and artwork is just so S-tier
JLol, man what a quote "the security, reliability, stablity, this is really not for me."
Jand the container jank is kind of self inflicted, lol.
J"all these containers are complicated."
Jso don't use them, he's only using them because he's trying to turn it into a package distro.
Ptold you, they don't know 
Jyeah this is the benefit of not being an immutable distro, we can skip all of this
Jlooks good though, vanilla's adwaita game is so good, heh
SAtomic Cloud Native! ftw rofl
SAlso 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
RHuh, I posted this in another server today
RIt's a disaster waiting to happen, really. I hope Microsoft decides to restrict kernel access, it might be necessary at this point
Slol great minds and all that!
STbh I'd rather not have stuff trying to inject/monitor my kernel but maybe thats just me 
SGive me back the days of punkbuster and gamespy 
Myou called?
Qtbf, 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.
KTo me that's just a container file build
KMake your own image from one of ours
KI see no reason to add any other baggage to that relationship
KThe alternative is going down the same path nix did and overcomplicating something that should be simple
KGitHub
Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.
QThat 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.
Jwhy not use nix to generate the container image?
JThere's tons of tools to generate container images, using bash and containerfiles is just our approach
Ryou already tested it? damn, i was looking forward to VRR....
QBecause 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.
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.
PI don't care much about NixOS, just pointing out that declarative configuration existed before. Not talking exactly in OS scope here.
RFedora peeps reporting that the new 560 works fine now, games and all
RI know Kyle had a terrible experience but did anyone else here give it a try too?
