Deleted Comment
The seatbelt laws are not archaic by any meaning of the word, and they can be justified with rational arguments.
Care to try doing the same for family thing? Aside from tradition.
(I'm not supporting the argument, just saying that it's not hard to come up with a plausible rational one)
One of the use cases is to have a development db that can get data from production or staging (and doesn't send local changes back)
What I've done usually is have some script/cron/worker run periodically to get data, either via dump or running some queries, create a snapshot, store it in S3, then have a script on the local dev code that gets the snapshot and inserts/restores the data in the local db. This works for many cases, but index building can be a pain (take a long time), depending on the data
I haven't written any Zig but these demonstrations give me strong vibes of how I felt when I picked up Go more than 10y ago.