muti

10,000 throws with small perturbations in the starting conditions should be distributed evenly across all sides of the die.

Alternatively you could use RNG to generate a fair result, simulate the throw, and then set the sides of the die to produce the result from RNG. This is all academic though and I imagine anyone using the site won't be bothered.

Darktable keeps the old modules around but hides them, opening a file processed years ago will still go through the pipeline with the base curve module and come out the same. As a bonus, it is possible to use "obsolete" modules that may handle certain images better, achieving a particular look, or you are comfortable with the older module and prefer not to use the new replacement.

  podman quadlet list

  podman system migrate --migrate-db

https://heresgolden.com/products/golden-g2-mens?variant=4362...

  Images printed with structural colour ink can be made both highly transparent to transmitted light (top) and at the same time reflect light from above in vivid colours (bottom) – two properties that are typically considered mutually exclusive

We know these models can solve much more difficult problems, something isn't right.

What's funny is how much better I understand git now, and despite using jj full time, I have been explaining concepts like rebasing, squashing, and stacked PRs to colleagues who exclusively use git tooling

IIRC it is intended to be read as SQL-ite, as having some relationship to SQL.

PG Lite probably makes sense here though, and PGite is not appealing

There's also the compact, simple alternatives to bulky receivers that are becoming available: Wiim amp, Sonos amp, Eversolo play, and the cheaper chinese makers like SMSL and Fosi. Each of those brands has a small device the size of an apple tv that will take an HDMI Arc input, and output an amplified signal to power some passive bookshelf speakers.

In my experience with jj when resolving a conflict, as long as I do it in the earliest change, I will only have to do it once.

Git has the rerere setting [0] which reduces the need to resolve the same conflict over and over

0: https://git-scm.com/book/en/v2/Git-Tools-Rerere

  if (!same) {
    return;
  }

  if (!number) {
    return;
  }

  if (!of_braces) {
    return;
  }

  println("but easier to read")

Yes you would need to carefully design the system that allows deletion of keys while minimizing chances of data loss, but it can be done, and it's going to be cheaper and less complex to do so on a tiny subset of the data.

Latency considerations are also down to design, it's not a given that there will be significant overhead imposed.

Containers auto update with built in podman tooling, getting at logs and monitoring is through the usual systemd tools. When I need to change something, it's easy to work out where the config files are if I have forgotten and they are easy to read and change. Rootless and daemonless is nice too.

I tried a few things along the way, podman compose felt clunky so I'm glad it is deprecated and it's clear quadlets are the way to go.

There was a learning curve and there's less information out there than with docker, so keep that in mind. I would still lean towards docker and docker compose for local dev to bring a stack of services up and down.

1. https://github.com/Bastardkb/Charybdis

> Apple isn’t wrong here. The Mac mini measures 5 x 5 x 2 inches, compared to 7.75 x 7.75 x 1.4 inches from the last generation; it takes up much less space on your desk, which is great. The trade-off is that you run out of space for some important things, like a power button.

Ultimately it comes down to how much effort you want to spend categorising spending, but there are many levels of granularity and orthogonal dimensions to slice against