There was a post earlier today complaining about questions that aren’t open-ended, and therefore don’t adhere to the community rules. So here we are with a question with many possible answers (which makes it properly open-ended).

Probably not directly helpful, but Nix packages for Chromium and Electron apps are set up so that you can switch to native Wayland mode globally by setting an environment variable, NIXOS_OZONE_WL=1

I don’t know of any global setting that isn’t distro-specific.

The artificial sounds are legally required at low speeds, at least in the US and Europe. In the US electronic sounds are required at speeds below 30 kph. In the EU I think it’s 20 kph. At faster speeds the sounds of wheels on the road and such make electric and hybrid cars basically as loud as ICE cars.

There are very specific rules about the noises. It looks like there was some effort in the US to allow user-selectable sounds, but it didn’t work out. I found some info here, https://www.federalregister.gov/documents/2022/07/13/2022-14733/federal-motor-vehicle-safety-standards-minimum-sound-requirements-for-hybrid-and-electric-vehicles

This seems like the right answer to me. Whether or not you decide to dual boot, make one of these USB keys so you can recover if something goes wrong.

When I was using Debian I found I could generally get the latest version of software I wanted from Nix if it wasn’t in the main Debian repos, or was outdated. Nix works quite well on any Linux distro - it doesn’t interfere with the rest of the system.

All I can tell you is that this is done differently for each shell. So decide whether you want completions for bash, zsh, fish, all of the above, or whatever, and look at the docs for the relevant shells.

There are other galaxy clusters. Gravitational binding is not unique to the local cluster. From Wikipedia,

Notable galaxy clusters in the relatively nearby Universe include the Virgo Cluster, Fornax Cluster, Hercules Cluster, and the Coma Cluster.

The expansion of the universe is very tricky to explain. Oversimplifying can lead to an explanation that seems to be contradictory.

This is why I switched to labelling USB sticks with two-character codes, and I keep a file that lists the current content of each stick.

I think this is good advice. Don’t over-think it!

Good to know! I’ll put the Ibis and fruit bat on my Australia bucket list, along with a Huntsman. Although the latter are so widespread that I’ve probably already seen some living in America. But I’m guessing the Australian Huntsmen are a bit different from the North American ones.

Anyone else read these newsletter titles in Pixlriff’s voice? “This week, in Hermitcraft Gnome!”

Modern frameworks like Playwright do a good job of avoiding those waits. So the tests are less flaky, and are faster.

There’s a relevant community post, NixOS is not dying, please don’t spread fear actively

I tried Linux in college because it was a hot thing there. Been hooked ever since.

I’m not a distro hopper. I used Debian Testing for many years. Last year I switched to NixOS because it was a compelling value proposition for me. I’m very happy with it!

iOS also supports third-party passkey managers so that’s an alternative to Android for helping to fill gaps creating passkeys.

Nice! I may take a look. I’ve been happy with Enpass except that I recently switched to a window manager that doesn’t implement xwayland, and Enpass is one of only two apps that I haven’t gotten working in native wayland mode, or found a substitute for. So I’ve been running Enpass in a rootful xwayland window running a nested i3 session. The IPC connection to the browser extension still works so it’s not too bad, but I’m a little tempted to try alternatives.

I forgot to mention that to use a passkey manager on Android in addition to setting that Chrome feature flag you also need to set the app as your passkey manager. That’s done at the system level in Settings > Passwords & accounts > Passwords, passkeys, and data services

FYI I’ve been running Steam and Wine games in Gamescope because I’m using a window manager that doesn’t implement XWayland. I don’t know if that would help with Nvidia, but might be worth a try. It works ok; Gamescope has a Steam integration switch that helps.

I think Electron apps mostly switch to native Wayland mode if you set an environment variable, ELECTRON_OZONE_PLATFORM_HINT=wayland. The one I don’t have working in Wayland mode is Discord. See https://wiki.archlinux.org/title/wayland#Electron

A commit followed by a reset or commit --amend later is one more step than a worktree --add. Plus there have been lots of times when I’ve had some changes staged, and some unstaged debugging or experimental changes that I want to make sure not to commit, and thinking about how to pack all that away neatly so I could get back where I was seemed sufficiently obnoxious that I avoided doing whatever would have required a quick branch switch. Worktree would have let me pick up where I left off without having to think about it.

I’ve been using the newer commands like switch and restore for a while. But I learned a few things here that will indeed make my work easier.