| 3 Apr 2026 |
 emily | also | 23:10:19 |
 samasaur | could just remove /var/folders/* entirely, no? or at least remove the T at the same time | 23:11:25 |
| emily | /var/db/diagnostics should be at least largely discardable I think (maybe sudo log erase --all will do it? I would be scared to just delete the files though). /var/db/SystemPolicyConfiguration I expect might be something funny about remembering Gatekeeper stuff for a trillion binaries from builds a day or something but that's just a guess. also completely separate but when comparing cores for base vs. pro CPUs remember that those 10 cores are split between P and E cores although Apple Silicon E cores are still plenty fast. | 23:12:45 |
| emily | just e.g. if you divide it up 5 / 5 for big-parallel or something it might not be great | 23:13:44 |
 Randy Eckenrode | I think I have a fix for the dotnet crash on macOS 26.4. I’m building darwin.ICU with a custom version suffix for the icu namespace. Since the C++ API isn’t ABI stable anyway, this shouldn’t break anything. | 23:13:59 |
| emily | should we maybe just expose the SDK ICU stubs? I think I've seen stuff call into it even before Tahoe. in general building stuff that the system frameworks can plausibly use seems like it's a lot of latent potential pain similar to the libc++ fun we have | 23:15:12 |
| emily | esp when we only use it for stuff that needs the weird Apple fork | 23:15:29 |
| Randy Eckenrode | System ICU expects to read from /usr/share, which is a pain with the sandbox. | 23:15:33 |
| Randy Eckenrode | Also, Linux will need darwin.ICU for Swift. | 23:15:44 |
| emily | though doesn't this imply that our own libxml2 will also clash? 🫠 | 23:15:49 |
| emily | (allow file-read* (subpath "/usr/share/locale")) | 23:16:09 |
| emily | IIRC it's been allowed for a long time | 23:16:33 |
| Randy Eckenrode | ICU needs /usr/share/icu. | 23:16:49 |
 hexa | ok, log erase --all might just go in a launchd timer | 23:17:12 |
| hexa | yeah, it's funny how greedy apple is with cores | 23:17:27 |
| hexa | how else are we supposed to slice them up then? | 23:17:43 |
| emily | hmm are they? I feel like the average Windows ultrabook doesn't ship with 10 cores of anything but maybe I'm behind the times :) | 23:21:12 |
| emily | at the high end ofc is a different matter | 23:21:22 |
| emily | but direction there is very much towards clusters (e.g. there's RDMA over Thunderbolt now) | 23:21:42 |
| hexa | right, I'm probably comparing apples and oranges | 23:21:45 |
| emily | well tbh I guess with 5 + 5 you might get both using 4 P + 1 E which would be just fine | 23:22:44 |
| emily | er | 23:22:57 |
| emily | sorry I mean 2 P + 3 E | 23:23:06 |
| emily | what I mean is that M4 → M4 Pro looks like just 10 cores → 12 cores | 23:23:27 |
| hexa | oh, but it has many more P cores | 23:23:38 |
| hexa | I see | 23:23:39 |
| emily | but it's actually 4P → 8P, 6E → 4E | 23:23:40 |
| hexa | good call | 23:23:47 |
| emily | also higher memory bandwidth etc. | 23:23:48 |
| emily | so the perf differential may be higher than you expect | 23:23:53 |
