Currently 260k loc in the workspace
- 1 Post
- 5 Comments
So there’s this fun thing in rust where if you don’t have exactly the same feature set for all components of the workspace when you go to a subfolder for a component you can invalidate cached artifacts and trigger a lot of jobs. Same thing when you check out a branch then compile. And as I have a fair volume of crates in the workspace, changing mtime on the files for a checkout means I still have 5~10 minutes each time I want to run tests locally (a fresh run takes ~30 minutes to ~45}
I looked at phoronix benchmarks for the 13 Pro first, but I wasn’t impressed (even acknowledging that Phoronix should have asked for the Ryzen one)
I’m not even using it for AI or heavy local inference or so. I just happen to easily fill up and use 40-is GB, and when I want ram in a package that performs well CPU wise it gets giga expensive fast :(


I meant that I don’t care about battery life/speakers/screen, it’s only a tiebreaker if all other things (price, CPU sustained perf) are mostly equal.
I missed the memory part indeed, going up to 64GB changes a lot, I haven’t found a HP g1a with ~48GB of memory which is what I think is the good amount for…
…My budget which is 3000-3500 EUR
Indeed I’m in France
Thanks for those links, I knew GB was flawed (mostly because it’s user-provided data, if nothing else), but had no idea about alternatives