thomas_viaelo

Same. Matt Gallagher's posts on Swift concurrency and Cocoa memory ownership are still the clearest writing on those topics anywhere. This post is still the right answer to a Stack Overflow question I haven't asked yet.

Did you weigh home screen widgets here? For "log mileage when you refuel", a one-tap widget feels much closer to the moment than open Safari, find the bookmark, hit the button. PWAs on iOS still can't put one on the home screen. Curious if cross-platform was the call from the start, or if widgets came up at all.

Mostly yes. If `tar` resolves to gtar in your PATH, your archives won't carry the LIBARCHIVE.* xattrs that GNU tar can't decode, so the warnings go away.

One thing that still trips me up though: `._Foo.txt` AppleDouble files get created in your filesystem any time something Finder-adjacent touches a folder, and gtar archives them just fine, but they show up as garbage on the Linux side. `dot_clean -m mydir/` before tarring kills them, or you can pipe through `--exclude='._*'` if you don't want to touch the source tree.

Curious whether you've tested the popover with VoiceOver yet. Menu bar SwiftUI apps usually nail the status item by default, but the popover content tends to be hit-or-miss depending on row layout. A stack of Text views walks cleanly, but custom-drawn rows often read as one blob. Worth confirming for jareds' use case.

Does the LLM auto-tagging and embedding pipeline run on the device, or are they remote calls?