The message is still to use the PulseAudio and JACK APIs. They are proven and they work and they are fully supported.
I know some projects now use the pw-stream API directly. There are some advantages for using this API such as being lower latency than the PulseAudio API and having more features than the JACK API. The problem is that I came to realize that the stream API (and filter API) are not the ultimate APIs. I want to move to a combination of the stream and filter API for the future.
Switching over to the discrete GPU work in the efi/bios might help. Optimus (the driver that chooses between discrete and integrated) is known to be a steaming pile.
PipeWire wins in the feature-set game, which is why it is being preferred over PulseAudio.
According to the inventor of PipeWire, this is the wrong perspective to take. PipeWire is preferred over PulseAudio as a server, clients (apps) should continue to use the PulseAudio/JACK APIs because the PipeWire API is not designed for general use (it’s designed for things like pipewire-pulse and pipewire-jack).
I use NixOS on my personal machine and nixpkgs on my work Ubuntu (22.04 LTS). In the absence of NixOS I would not be using it: it somehow breaks all the file (open, save, etc.) windows, causing any app that tries to open one to crash (particularly annoying for browsers).
Not to mention the wrapGL issue.
It needs more polish on “genericlinux”. I did previously use it on MacOS, and it did make MacOS almost bearable - definitely years ahead of brew.
GPU drivers. It uses the Ubuntu 22.04 (LTS) userspace side of drivers. Could be incompatible with your kernel. Had all sorts of graphical weirdness with my AMD GPU with flatpak Steam.
Grubby is a good example of someone who was recently reformed. In one of his early Dota 2 videos (some time last year), he admitted that he didn’t know that games outside of Blizzard had gotten so good - he actually only played Blizzard games and nothing else. It’s been pretty wholesome watching someone learn the wider gaming world.
Silverblue doesn’t solve the same problems as Nix, or Ansible for that matter. I built my own in the past and it was non-trivial - although the CI process could pair quite nicely with Ansible. IMHO the primary advantage of Silverblue is that updates are a download, with practically zero work to do after the download has completed (this is a very big deal for RPM-based systems because an update boot can take a long time).
As for Ansible vs Nix, try switching from one program to another across all your machines. It’s doable but not fun. Now try switching back across all your machines. Nix makes your system equal a configuration, it does not add configuration.
You’re being down voted because Apple supporting old hardware is the only thing that Apple is good about. Would have done well in almost any other thread.
As an EV zealot I 100% support tinkerers, racers, and people who simply love the spirit of an ICE. But not in commuting/traffic, where nobody is enjoying anything anyway.
100% this. I’m passionately on the other end of the spectrum, where a car’s entire purpose is to get me from A to B without fanfare, prestige, or hassle. Also needs the birds eye camera because fuck parallel parking. Trains are a better way to do all that. And we should be moving more good with trains. Trucks are expensive and should be last mile exclusively.
The problem for most people is that trains, and other public transport, don’t take you from doorstep to doorstep. God help us all if we have to walk 1/4 mile to a stop. There is also politics preventing it, at least in America.
Things have changed since those days fam. For example, if you install Steam on Ubuntu (snaps) today it’s highly likely to break. If you want a solid Ubuntu recommendation go with the downstreams: Mint, PopOS, etc.