←back to thread

94 points justin-reeves | 2 comments | | HN request time: 0.416s | source
Show context
postalcoder ◴[] No.46005113[source]
As a former metadata completionist, my mind starts to dissociate when I think about my battles with EXIF metadata, vendor-specific metadata, and the way different software supports, or refuses to support, any of it.

It gets even worse when ingesting images into Apple Photos, where you have to confront papercut bugs that you know will never be fixed.

I love ExifTool. It’s one of the great utilities. It works for almost every file I throw at it. But reading its output can be unsettling. It’s like getting a glimpse of eudaimonia, only to have it rudely interrupted by the reality of Apple Photos misreading every lens in your collection.

replies(4): >>46005520 #>>46005609 #>>46006247 #>>46006517 #
concinds ◴[] No.46006517[source]
> It gets even worse when ingesting images into Apple Photos, where you have to confront papercut bugs that you know will never be fixed.

I wish they open-sourced their built-in macOS apps.

replies(1): >>46006605 #
1. pstuart ◴[] No.46006605[source]
A nice compromise would be to open source the libraries that consume and emit data as well as core processing. Then they can add their own secret sauce UX and integration.

Likewise, that will never happen either.

replies(1): >>46008953 #
2. AlanYx ◴[] No.46008953[source]
Yes, they used to compromise more along these lines in the past. e.g., Samba's vfs_fruit would never have gotten as good as it is without Apple open sourcing their SMBClient. Everyone benefits, even Apple (I'm sure they're running vfs_fruit on their server storage arrays internally). Wish they'd do it more.