Mystery: solved!
Note to self: The Library folder should not be measured in GB...
With Dad's assistance, I went around poking at Zachary's innards from the command line. In some ways, it's a lot easier to look at memory allocation from there--just type du -s *. The units are really wonky, but you can still tell relative size. You can also see /private and various other folders that aren't accessible from the GUI--explain why my calculations never added up. And that's when we noticed that my Library was WAY bigger than Dad's. Specifically, the Logs folder: his was 3,828 (units)... mine was 17,621,904. Uf da.
While I was trying to see if I could use XCode for CS 60 work, I opened one of my CS 5 programs to see if I could cannibalize it for my 60 assignment. Didn't work... and now I find out, the CS 5 program started up, got input from hell knows where, and reeled off a zillion errors. Without me noticing.
Anyway, we deleted the logs, and now I have 13 gigs of delicious space! Yayyy!
With Dad's assistance, I went around poking at Zachary's innards from the command line. In some ways, it's a lot easier to look at memory allocation from there--just type du -s *. The units are really wonky, but you can still tell relative size. You can also see /private and various other folders that aren't accessible from the GUI--explain why my calculations never added up. And that's when we noticed that my Library was WAY bigger than Dad's. Specifically, the Logs folder: his was 3,828 (units)... mine was 17,621,904. Uf da.
While I was trying to see if I could use XCode for CS 60 work, I opened one of my CS 5 programs to see if I could cannibalize it for my 60 assignment. Didn't work... and now I find out, the CS 5 program started up, got input from hell knows where, and reeled off a zillion errors. Without me noticing.
Anyway, we deleted the logs, and now I have 13 gigs of delicious space! Yayyy!