The assumption was that nobody used win8 lol
But again I think people who grew up with 10/11 are more likely to use the windows store than you think. They used an iPad before they got a chromebook before they got a windows computer. My little cousins don't play minecraft Java, they play minecraft bedrock. I don't think they know what VLC is.
Ok fair, last time I used windows you had to install gpu drivers manually. I think you still are recommended to do so, since the windows ones are really old.
But yeah manual driver installation/specialized distros for Nvidia is a problem that's in the process of getting fixed with NVK, Nova, and the official drivers. Intel and AMD are there already.
I would rather have one extra manual step like that than dealing with/paying for Windows 11
Yeah I think in the future, we'll figure out how to make NixOS configuration modular enough to be viable for laymen, but Linux Mint works well enough for Windows refugees.
Linux mint has an app store like Windows, MacOS, iOS, and Android.
I think it supports flathub, which has every app you could need, but I haven't checked since I run a very customized NixOS.
People don't really download .exes anymore, it's just people who are used to windows 7 and earlier who still do that.
Pre-installed Nvidia drivers will likely be fixed in the next two years, but:
B. The 25% of gamers not using Nvidia GPUs do not have driver issues on Linux
III. Windows has tons of driver issues, so I'm not sure why Linux Nvidia drivers are a significant detail here. We don't expect little Jimmy to know to install drivers, and know what to do when windows update fucks your drivers randomly. Linux actually soves those issues for you.
That's a weird way to spell Linux Mint
not to mention there are 48 and 64gb dimms out now too that work with basically all alder lake atoms
Yeah, what you're talking about is called GitOps. Using git as the single source of truth for your infrastructure. I have this set up for my home servers.
nodes has NixOS configuration for my 5 kubernetes servers and a script that builds a flash drive for each of them to use as a boot drive (same setup for porygonz, but that's my dedicated DHCP/DNS/NTP mini server)
mikrotik has a dump of my Mikrotik router config and a script that deploys the config from the git repo.
applications has all my kubernetes config: containers, proxies, load balancers, config files, certificate renewal, databases, clustered raid, etc. It's all super automated. A pretty typical "operator" container to run in Kubernetes is ArgoCD, which watches a git repo and automatically deploys any changes or desyncs back to the Kubernetes API so it's always in sync with git. I don't use any GUI or console commands to deploy or update a container, I just edit git and commit.
The kubernetes cluster runs about 400 containers, most of them just automatic replicas of services for high-availability. Of course there's always some manual setup steps outside of git, like partitioning drives, joining the nodes to the cluster, writing hardware-specific config, and bootstrapping Argocd to watch git. But overall, my house could burn down tomorrow and I would have everything I need to redeploy using this git repo, the secrets git repo, and my backups of my databases and container /data dirs.
I think Portainer supports doing GitOps on Docker compose? Never used it.
https://docs.portainer.io/user/docker/stacks/add
Argocd is really the gold standard for GitOps though. I highly recommend trying out k3s on a server and running ArgoCD on it, it's super easy to use.
https://argo-cd.readthedocs.io/en/stable/getting_started/
Kubernetes is definitely different than Docker Compose, and tutorials are usually written for Docker compose.yml, not Kubernetes Deployments, but It's super powerful and automated. Very hard to crash once you have it running. I don't think it's as scary as a lot of people think, and you definitely don't need more than one server to run it.
nah you're probably not going to get any benefits from it. The best way to make your setup more maintainable is to start putting your compose/kubernetes configuration in git, if you're not already.
Ah, no, Kopia uses a shared bucket.
Seems like a good way to do it.
Keep in mind Kopia has some weirdness when it comes to transferring repos between filesystem and S3, so you'd probably want to only keep one repo.
https://kopia.discourse.group/t/exported-s3-storage-backup/3560
Backblaze B2 is a cheap S3 provider. Hetzner storage box is even cheaper, but it doesn't support S3 natively, so you're likely to run into issues with the kopia repo compatibility I mentioned.
steam hardware survey shows 17% AMD and 8% Intel