I've been using TTS systems for decades with accessibility use cases, so other than quality audio books that necessitate a skilled performing narrator, I no longer mind.

In fact, I prefer legacy Bayesian phonetic models over the newer convolutional and recurrent neural networks, as their hard consonants and robotic consistency in pronunciations and intonation are much easier to listen and discern at higher words per minute, like at 3x or 4x natural speech rates for everyday blind reading, as compared to modern mumbling/slurring of syllables or artificial stridor and other breathy sounds.

I recall the author saying they're not a native English speaker, and preferring international intelligibility over regional voice-over, plus the production convenience while traveling and script writing without a quiet audio recording environment. See around 7 min mark:

• The most common question on my channel - Core Dumped
  • https://youtube.com/watch?v=FlOVA8NLGDQ

Do you know of a complete example or live config I could read through as a reference for that first method recommended?

I'd also be interested in complete examples for a working pair of remote builder and local client (both NixOS multi user), as all the documentation I've come across thus far are either:

• intent on modifying root ssh configs in spite of security practices

• botch use of substituters on the remote builder

  • causing needles recompilation, ignoring upstream cache.nix.org

• is awkward or incompatible with non-interactive sudo sessions

• works for nixos build but not to switch

• https://nix.dev/manual/nix/2.30/advanced-topics/distributed-builds

• https://wiki.nixos.org/wiki/Distributed_build

• https://discourse.nixos.org/t/nixos-rebuild-use-remote-sudo-prompts-me-for-a-password-3-times/56003

• https://discourse.nixos.org/t/remote-nixos-rebuild-works-with-build-but-not-with-switch/34741

From the video notes, this alternative to nix-serve looks promising:

• https://github.com/nix-community/harmonia

FYI, VSCode can now natively show commit info inline, no GitLens extension required:

https://code.visualstudio.com/docs/getstarted/tips-and-tricks#_git-blame

Mainly the official git CLI for controlling branches and sub modules, and sometimes the GitHub CLI if quickly checking out a pull request from a forked repo.

Also use the source control tab in VSCode rather often, as it's really convenient to review and stage individual line changes from its diff view, and writing commit messages with a spell check extension.

If it's a big diff or merge conflict, I'll break out the big guns like Meld, which has better visualizations for comparing file trees and directories.

About a decade ago, I used to use SmartGit, then tried GitKraken when that came around, but never really use much of the bells and whistles and wasn't keen on subscription pricing. Especially as the UX for GitHub and other code hosting platforms online have matured.

If you just want to quickly create a local python develop environment on the side using Python module metadata, installing uv from nixpkgs, and enabling nix-ld to run pre-compiled binaries from PyPI keeps things simple, and replicating the same virtual python environment workflow you to have on any other distribution:

https://discourse.nixos.org/t/i-want-understanding-nix-packages-and-flake-basics/67365/3

If you wanted to package a python module for nix or for proper distribution via nixpkgs, you'd want to add a nix derivation file that encapsulates all the inputs, i.e. software building materials (SBOM). There are existing nix library functions that can automate most of the packaging, not unlike Debian macros:

https://wiki.nixos.org/wiki/Python

The second approach is more rigorous, and combined with something like flakes for pinning the exact hash for all inputs via lock file ensures reproducibility, like when sharing with other nix users. While as the first approach is more subject to your current system, i.e. linking to whatever system wide libraries are presently installed, but it's less upfront effort to reuse existing python-package-managers than to nixify everything.

What user software are folks using to monitor and log PSU sensor data?

Would be nice to correlate power usage and efficiency with system load percentage over time and type (CPU vs GPU).

I'll preface that NixOS may not be for everyone, as deviating from a conventional hierarchical file system is a radical departure from conventional distributions; but for those that want precise control over their system environment, it has a good deal of appeal.

For example, I appreciate being able to use the latest bleeding release of a number of tools while sticking with older trusted versions of other utilities, but if both relied upon different versions of similar dependencies, such package conflicts can be troublesome to resolve, as few Linux package managers gracefully deal with multi version installs.

For NixOS using the nix store, installing leaf packages that traditionally conflict is trivial, and as a user, I can spend less time managing every transitive dependency in order to use the software I want. Not having to wait for a disjointed ecosystem of packages to synchronize around dependencies, or resorting to compromise in package version selection is very liberating.

• https://nixos.org/guides/how-nix-works/

The functional language and documentation for nix itself is a bit quirky, as I wish it was stronger typed, but being able to declaratively express and version control my setup across workstations has been a time saver; installing/configuring something once and then have-done with it.

I think it stands for Managed Service Providers.

Nix-ld is only used by unpatched executables that use the link loader at /lib or /lib64. If you use for example python from nixpkgs than it will not pick up NIX_LD_LIBRARY_PATH and NIX_LD since these types of binaries are configured to use a glibc from the nix store.

• https://github.com/nix-community/nix-ld/blob/bc1a7a1b88589bfd26846fc5341fe44fc73b3fbd/README.md?plain=1#L164

Ah, I guess that's why I've seen folks recommend just having uv install the python interpreter as well, so everything python uses the same link loder from nix-ld.

I would have liked the PyCon25 talk directly, but I don't think the recordings have been published yet:

https://slides.com/bittner/pycon25-nixos-for-python-developers#/2/4

Hopefully the presenter discusses more on their later slides in using python on NixOS and working around python packaging's use of dynamic linking.