←back to thread

211 points l8rlump | 4 comments | | HN request time: 0.416s | source
Show context
dylan604 ◴[] No.44506331[source]
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.
replies(2): >>44506609 #>>44506622 #
1. ethan_smith ◴[] No.44506622[source]
Sidecar files (like XMP) are the industry standard for non-destructive RAW editing - they maintain file portability between different apps and preserve your original files. Library-based approaches offer better performance and organization but create vendor lock-in and complicate backups.
replies(3): >>44506976 #>>44508852 #>>44509865 #
2. vladvasiliu ◴[] No.44506976[source]
Aren't edits app-specific anyway? Last I tried (a month or so ago) sharing edits between darktable and lightroom didn't exactly work.
3. runxel ◴[] No.44508852[source]
That's why I love DNGs. No Sidecar file to lose! Just one file, and still non-destructive.
4. dylan604 ◴[] No.44509865[source]
Great, so if I use an app that creates XMP files, this app is going to create a second sidecar called rrdata. So I guess I could have amended that to the original question on why create a different sidecar than the images’ default.