I include video [1] and audio (.m4a) [2] files via EXIF.
For text files [3], I add a JSON block at the top to mimic EXIF.
I don’t want to deal with an additional sidecar file per asset. The risk of losing one during a transfer between systems is too high. It’s a conscious decision and not an oversight.
The problem I have with Garmin is lack of support for older devices. They practically bricked my old bike computer. Unfortunately it's been awhile and I can't recall the details of the issue. I have since switched to Wahoo but have only had it for about 3-4 years now.
I think it was 3.3x where things started working. I don't recall 4.x being around much. I do remember 5 and 6. For some reason 4 never made a splash in my circle of friends.
It took more base memory than ever. It had a complicated code page system that most people didn't want, and a clunky early version of IBM DOSShell that was scorned although it grew into something useful.
But it supported disk partitions over 32MB, and for that reason, it was reluctantly adopted. If you had a 286 or 386, then there were measures that you could take with a memory manager to make it not so bad, but on 8088/8086 class hardware, it didn't leave enough free memory for many big apps to run.
In my market you can’t plug into the ONT because it still requires authentication.
The modem the ISP provides has hard coded settings to limit connection counts as well as rate limit and probably other things. There is a reason they sell full duplex gigabit for so cheap, there are gremlins in the hardware.
reply