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.

> Ceramic Shield front, Textured matte glass back and stainless steel design

https://support.apple.com/kb/SP875?viewlocale=en_US&locale=e...

https://www.git-scm.com/docs/git-clone#Documentation/git-clo...

The size definitely gets bigger with each iteration:

  $ echo text >0.txt
  $ for i in {0..9}; do                             
  gzip <$i.txt >$((i + 1)).txt
  done
  $ ls | sort -n | xargs -n1 wc -c
       5 0.txt
      25 1.txt
      46 2.txt
      69 3.txt
      82 4.txt
     105 5.txt
     120 6.txt
     143 7.txt
     161 8.txt
     184 9.txt
     207 10.txt