Darktable editing workflow is centered around modules. Exposure, denoise, various color adjustments, etc are all separate modules. Dynamic range compression (and other common operations) has several implementations: base curve, filmic, sigmoid, and AgX. They all essentially do the same thing but have effectively superseded each other as they were added to newer releases.
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.
Thank you for prompting me to try with my own obscure question, Fable was able to find something from a poor description. I've been looking manually and over many sessions with different models as they improve, none have been able to find what I was after. Fable 5 just one-shot the answer.
Cool, been running my home server on podman + quadlets for about two years now and picked up a couple of things in the release notes
podman quadlet list
Added in v5.6.0, lists quadlets and their containers
podman system migrate --migrate-db
Flag added in v5.8.0. I remember seeing the bolt db deprecation warnings in the past but there was no tool to do the migration to sqlite, now there is (or just upgrade to podman 6.0.0 and it will do it automatically)
See the image and caption at the top of the article
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
The printing on the phone is not visible when the phone display is on as the structural printing is highly transparent. When the display is off, the printing is visible because of the reflected light.
Doesn't seem like a very insightful result. Kimi won with the naive strategy. Other models didn't slide tiles at all or didn't demonstrate understanding of the rules, claiming words that lost points. A strategy that did nothing would beat them.
We know these models can solve much more difficult problems, something isn't right.
+1 on this, I also switched to jj when working with any git repo.
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
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.