I’ve got two steam controllers on their last legs. I can’t go back to shitty traditional controllers.

While this is broadly true, -O3 doesn’t have as many downsides as it used to, so some distributions are considering to move to it (like Ubuntu).

It was a mess in the early days, though, with not just performance issues but outright crashing being a common problem.

Maybe post an issue report on their github. The queue function does work on desktop at least (the web client), but I don’t bother with playlists.

I tested it with 6.11 and the performance was kind of bad but it could have been a one off. I’m generally happy with full preemption though.

The issues are mainly under high CPU load. A RT kernel will continue to maintain low latency without xruns but a normal kernel may not. The compromise option is full preemption which generally does a good job but doesn’t have the issues with throughput that can occur with a RT kernel.

Although maybe you meant full when you indicated a preemptive kernel (voluntary preemption is still the default I believe but it’s kernel dependent).

There’s a player queue functionality (which works kind of like a playlist) but I don’t think it transfers across devices. But you can at least queue up a bunch of tracks on a device.

Audiobookshelf also supports podcasts (and ebooks, but I haven’t tested that).

Hopefully it can actually preserve packages across updates which is incredibly annoying to have to handle manually.

EDIT: Just found about this attended sysupgrade package which should help until when/if the new package manager fixes the issue.

Morrowind. Although it’s more like play a few hundred hours every five years for me.

I use both 1 and 3, personally (although docker rather than podman). I normally prefer the nix way but it doesn’t support every service. I like that nix config is all in one place. In theory, so is docker-compose to am extent but there are usually exceptions and things can get complex. I also hate having to directly manage containers with minimal commandline tools.

But yeah the whole translate config routine in nix is kind of annoying, and I often need to experiment to get the options right if they aren’t documented.

0.82 is only two weeks old, so you would have needed nightly up until that point for most newer Garmin devices. I did uninstall Connect shortly after but I think you just have to make sure it’s not running, as I know some use both apps.

Gadget bridge doesn’t really work for any “new” (i might be wrong here) devices.

Most newer Garmin devices should work since 0.82 (and earlier with nightly). It’s not feature complete compared to using Gadget Connect but should be enough for most use cases, unless you really care about the social/awards aspect and some of the deeper metrics (although if you’re handy with SQL you can handle that yourself).

Not being able to set an event date and have “daily suggested workouts” follow that is my only annoyance, although I’ve been happy just using the defaults for now.

(What about options in flakes.nix? Should I search those on the flakes/options tab?)

Not quite sure what you mean here. I normally only configure out-of-tree packages as flake modules (or whatever the term is), and I don’t think there is an official collection/search page for these. It’s mainly that certain packages require it like lanzaboote, and home-manager for that matter.

Once I enabled home-manager, I saw that in ~/.config/nixos a flakes.nix and a home.nix files appeared. I already have a flake.nix and a home.nix files in my etc/nixos directory. What’s going on?

It sounds like you configured home-manager system wide, probably through /etc/nixos/flake.nix, but then called the home-manager executable. If you did configure it like this then you do not need to call home-manager ever since nixos-rebuild etc commands will handle this for you.

Does putting packages in configuration.nix use the version control flakes provide?

Typically, it will be configured to follow inputs.nixpkgs so packages will use versions of whatever revision is currently pulled. In my system that is:

inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";

and then you essentially pass that to configuration.nix, and home.nix.

And although you seem to already be using flakes, when you call:

nix flake update

a new revision of input.nixpkgs will be pulled, and so packages configured in configuration.nix will be updated when you next call

nixos-rebuild switch

or whatever you used to update your system.

Refer to: https://nixos-and-flakes.thiscute.world/

if you haven’t already as there is where I got started from for the most part. There’s a lot more detail I missed since nix and flakes are pretty complex (and I don’t fully understand much of it either).

System packages in configuration.nix, user packages in home.nix. I’d say anything that is non-interactive and/or requires root access is a good rule of thumb for system packages. Beyond that I try to use modules for configuring packges and there is usually only one of nixos and home manager options (sometimes there are duplicates).

As for flakes I mostly use it to handle a bunch of different systems from one config and any flake specific configs. I also use standalone flakes for dev environments but that’s not related to the system config.

You can actually play from the UI too, but it’s not particularly nice to use (or intended to be used that way).

I’ll add pinchflat as an alternative with the same aim.

It means the library of PC games. A bit like a Steam Deck can be seen as both a PC and a handheld console.

I’d like to see it show if there is any third party DRM as well, like the Augmented Steam extension does.

that I put on a SD card for my phone

Pretty soon you won’t be able to buy a phone without expandable storage. On the plus side, internal storage is going up, but it’s still not big enough to hold a complete FLAC collection if it’s a reasonably large library. You can re-encode your library just for phone usage, but that’s a bit annoying to maintain.

Also, I’ve found all of the offline music players on Android kind of suck, and don’t support the workflow I like or have bugs.

They might be concerned about future competition with a looming potential breakup of the company by the US DOJ (not that it would necessarily weaken Android itself but it seems plausible). But it could also just be because one of the devs wanted to do it, which is pretty typical with Google (for better and for worse).