tynorf
Joined 9 years ago
Joined 9 years ago
I suppose I didn’t specify exactly what I would recommend to someone who thinks it’s too hard, so here is that:
1. Install Backblaze. This is basically fire and forget. 2. (1) is enough for most people, but if interested (and on a Mac, which is what I’m familiar with), plug in an external SSD once a week or so for Time Machine. Setup involves clicking on the drive in the setup wizard and specifying an encryption password.
I don’t know about “ultra” robust, but this gives you protection from accidental deletions, natural disasters happening to your computer, hardware failures, and corruption from software bugs. The ongoing maintenance is plugging in a hard drive once a week.
If that is too much effort, just (1) provides natural disaster and hardware failure protection. It helps somewhat with the others but Backblaze only saves versions for 60 days and that’s a tight window to notice subtle corruption of e.g. your photos.
Really this should be devices full stop. Also, "backed up" should include no fewer than two backups on different media and in different physical locations e.g. Time Machine to an external SSD _plus_ continuous cloud backup.
https://ziglang.org/documentation/0.16.0/std/#std.heap.Arena...
However, some people think there are problems with this usage: (pdf warning) https://www.cidrdb.org/cidr2022/papers/p13-crotty.pdf
It’s kind of humorous that everyone interpreted the comment as complaining about Chrome. For all I know, it’s justified in using that much memory, or it’s the crappy websites I’m required to use for work with absurdly large heaps.
I really just meant that at least for work I need more than 8GB of RAM.
This is not true.
I'd argue all these "publish your DB schema as a GraphQL endpoint" frameworks that seem to proliferate have done a lot of damage to GraphQL's reputation. Strongly coupling data to presentation seems like such an obvious anti pattern, yet tools doing just that seem to be very popular for some reason.