> a personal challenge at the age of 18 ... with the support from Google Gemini

I'm no AI fanboy, but it's neat to see some dreams come true because of it.

Why the decision to store edits in sidecar instead of the app’s library? I’m sure there’s pros/cons that were considered, so curious how the pros won out.

Wild, I was literally just today looking at this repository to see how I could do raw image thumbnailing in Rust. Coincidences...

Looks very interesting. How much work would it be to get this code signed for the Mac?

Hey congrats on the app! This is just what I'm looking for :)

Just installed it on my m1 mac and opened a folder of RAW files. The initial loading lagged my whole macbook. Couldn't even open the dock. Once the thumbnails all loaded it's better but not as buttery smooth as I would have hoped! Would love to know what other commercial apps do that make them not lag. Is it just that they're written natively?

Will def keep an eye on things. If theres one 'must have' feature I can request, luminosity masking? Its hard to go back to raw editors that dont have it. Its not the end all or be all to masking (ie color, saturation masking, etc) but is def one the most useful to have access to without having to bust open PS or similar.

Already having a workflow for AI based subject masking is def nice to see.

The best raw image processing tool I know is called “RawTherapee”. It was developed by one or more absolute colour science geeks, it is CLI-scriptable, its companion RawPedia is a treasure trove of information (I learned many basics there, including how to create DCP profiles for calibration, dark frames, flat fields, etc.), and not to make a dig (fine, to make a bit of a dig) you can see the expertise starting with how it capitalizes “raw” in its name (which is, of course, not at all an acronym, though like with “WASM” it is a common mistake).

Beware though that it tends to not abstract away a lot of technicalities, if you dig deep enough you may encounter exotic terms like “illuminant”, “demosaicing method”, “green equilibration”, “CAM16”, “PU”, “nit” and so on, but I personally love it for that even while I am still learning what half of it all means.

I’d say the only major lacking feature of RT is support for HDR output, which hopefully will be coming by way of PNG v3 and Rec. 2100 support.

I'm glad there are an abundance of visual overviews in the readme. Too many readmes about GUI programs lack them (or they'll point to a site which still lacks a clear indication of how it behaves).

That said, they're all GIFs and each ~10-22MB. Making loading the readme larger than the program size itself. Embedding some video would be snappier.

In my opinion, a web based UI for something like an image editor is a bad idea. It will be slow and resource intensive.