691: A Menlo Phase
https://atp.fm/691
Apple's chip-fab options, branding the 20th-anniversary iPhone, Terminal and Xcode preferences, and some very special filenames.
Discussion
Replies:
12
Boosts:
2
@atpfm was the homework bit @marcoarment referred to the rec diffs #286? I think it must be but it wasn’t as long as I expected from the reference. (I had to try to find it because I’m having big feelings about homework right now).
@atpfm the Time Machine discourse in the past couple of weeks has been bizarre. Stating it corrupts itself regularly is a very strange thing to conclude, even with anecdata. Even more so given the often praised cloning alternatives use the same mechanisms.
@jimmyjamesuk Cloning apps like SuperDuper and CarbonCopyCloner do not use the same mechanisms as Time Machine to track, perform, and store their copies.
@siracusa The claim was that TM gets corrupted over time.These are just snapshots on an apfs volume. SD and CCC must be using these same mechanisms. In any case what on earth do you think these apps use to copy? Magic? It’s either asr or the file copy apis. The claim that TM corrupts itself is unsubstantiated. Feel free to ask Howard Oakley.
@jimmyjamesuk As for Time Machine corrupting itself, I’ve seen it with my own eyes many, many, many times. Feel free to search the Internet until you are satisfied that this is a thing that actually happens frequently enough to be a legitimate factor in backup strategy decisions.
@jimmyjamesuk And to be clear, by “corrupts itself” I mean Time Machine itself says that it can no longer back up to the destination, and it instructs you to start a new backup, abandoning all past backups. I’m not aware of any reliable way to recover from this situation without doing as it suggests.
@jimmyjamesuk The thing that gets corrupted is not the snapshot on the source volume (although snapshots can become corrupted), it’s the structures that store the multiple backups on the destination volume and the databases that track the state of those backups. SuperDuper just makes a single copy, so there’s none of that structure or database stuff, and CCC uses its own, different system to store and track multiple versions of files.
@atpfm I think @siracusa is over-complicating the node_modules backup problem. You don't exclude individual node_modules folders; you exclude your entire ~/Developer directory. Everything in there is either clonable from a public repo, a scratch project you don't care if you lose, or an important project pushed to a remote.
@kmcmahon Nah, I want my stuff backed up even between pushes.
@Daytonlowell I don’t think so.
