aw-clock VS exiftool-vendored.js

I’ve made my own desktop astronomical clock as a Raspberry Pi project, but that’s using a computer screen, it’s not a mechanical device, and at present has a very non-medieval look and feel: https://github.com/kshetline/aw-clock

Know that although ExifTool is written in perl, you can run it in "batch mode" which makes it quite fast--only a couple of ms to parse a file. I've written an open source library to manage the subprocesses for you if you're using node.js (and I also wrote the ruby variant ages ago):

https://github.com/photostructure/exiftool-vendored.js

The frontend is in Vue. Both the FE and BE are in TypeScript.

Parallelism is provided by https://github.com/photostructure/batch-cluster.js/

Metadata reads and writes are via https://github.com/photostructure/exiftool-vendored.js/

My more nerdier blog posts are tagged here: https://photostructure.com/tags/coding/

if you're looking into doing stuff with EXIF, there's a really good library that's also typed: https://github.com/photostructure/exiftool-vendored.js

I needed a good Node wrapper for ExifTool and wrote https://github.com/photostructure/exiftool-vendored.js

When I saw how slow it is to fork child processes in Windows, I then realized I wanted to run ExifTool in "stay-open" mode, which meant I needed to manage 1 or more long-lived child processes that communicate via stdin/stdout, so I wrote https://github.com/photostructure/batch-cluster.js

I also really missed scala's `lazy` operator, so I built that (and several other small, helpful functions/classes) that I documented here: https://photostructure.com/coding/uncertain-lazy-forgetful-a...