Indeed perhaps. I'd really like to see something like a Content-addressed Storage model from snix get upstreamed. That could really revolutionize bandwidth requirements for nix package updates and store sizes. Imagine downloading only the binary diffs for updates to packages like large modern browsers, IDEs, election apps, etcs, that mostly share common files across versions and packages. Suddenly, daily driving a rolling distro on the bleeding edge would be no more taxing on networks or disks than your average infrequent Debian update.

• https://snix.dev/

IBM acquired the company behind Fedora Linux. Although I doubt they had any corporate influence in the production of this particular vlog.

I wonder if they would have had better luck with Kubuntu or KDE Neon? Perhaps if they're still on KDE by the time KDE releases their Arch distro variant, they could test that too on their hardware.

Whoops, I misread scheme as schema. That's really powerful. One thing I wish I could reliably do with a Nix LSP is navigate to a definition of a symbol.

I think the other 99% would appreciate having some deterministic config, and not necessarily even using Nix either.

I'm kind of perplexed as to why no other distro hasn't already supported something similar. Instead of necessitating file system level disk snapshots, if the OS is already fully aware of what packages the user has installed, chron jobs and systemd services they've scheduled, desktop environment settings and XDG dot files, any Debian or Fedora based distro could already export something like a archive tarball that encapsulates 99% of your system, that could still probably fit on a floppy disk. Users could backup that file up regularly with their other photos and documents, and simplify system restoration if ever they get their laptops stolen or their hard drive crashes.

I think Apple and Android ecosystems already support this level of system restoration natively, and I think it'd be cool if Linux desktops in general could implement the same user ergonomics.

Let's say you're building a gaming desktop, and after a day of experimentation with steam, wine, and mods, you finally have everything running smoothly except for HDR and VRR. While you still remember all your changes, you commit your setup commands to a puppet or chef config file. Later you use puppet to clone your setup onto your laptop, only to realize installing gamescope and some other random packages were the source of VRR issues, as your DE also works fine with HDR natively. So you removed them from the package list in the puppet file, but then have to express some complex logic to opportunistically remove the set of conflicting packages if already, so that you don't have to manually fix every machine you apply your puppet script too. Rinse and repeat for every other small paper cut.

I find a declarative DSL easier to work with and manage system state than a sequence of instructions from arbitrary initial conditions, as removing a package or module in Nix config effectively reverts it from your system, making experimentation much simpler and without unforeseen side effects. I don't even use Nix to manage my home or dot files yet, as simply having a deterministic system install to build on top of has been helpful enough.

On top of that, it'd be nice for the Bluetooth spec to roll out a higher bitrate version of HFP, as it's common 16 kHz monaural configuration is awful when listening to multimedia while on video calls, like for remote watch parties or just listening to music or playing video games while hanging out on discord. I ended up just buying a USB to TRRS adapter with pass through Power Delivery in order to use my Android device with proper AV quality.

• https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Hands-Free_Profile_(HFP)

Personally, I've been happy using an LG TV for a single monitor setup. I have had to switch to KDE Plasma v6 for better font rendering given its unusual OLED pixel layout, as well as for native HDR support. But it's been nice to have a large physical font while still at default DPI. Although, I wouldn't't mind upgrading to 8K later when they get affordable, as the smallest 4K TVs at 42" happen to push the physical DPI down towards that of just 1440p panel.

https://programming.dev/comment/7921093

Wow, the COPY directive got a lot more powerful. I've been waiting for the --parent flag for years, while the --exclude argument is also a nice touch. Didn't know of the /./ pivot point before, but that's handy.

Before this, I've just been using a intermediary leaf stage within a multi-stage build process to copy the build context and filter the dependency lock files of the entire super project into a matching parent structure that I could then deterministically copy from.

I fell for it. It took me a minute into the game time to figure what was up and double check today's date.

Yeah, #4 is my favorite, and I'd be ok with #3, but I'd take #5 (or even #2) over #1, as all #1 icons look too similar at small scales.

For context, check the comments here for the discussions behind proposed options:

• https://programming.dev/post/149568

For those that don't know, Bogdan produces educational content for Rust, similar to others like:

• No Boilerplate
  • https://youtube.com/@NoBoilerplate