> I'm willing to compromise on battery life, and I don't need the fastest CPU, just a good quality work laptop where I can run `cargo build` / `docker pull` without worrying about filling up the disk, and mostly just a browser aside from that.
I know this isn't your point but this is exactly why I don't use docker--but I'm a bit surprised to hear you mention `cargo build` as something that might fill up the disk. I've been a vocal critic of Rust on Hacker News in the past, but the one thing I always thought they did very, very well, was Cargo and the tight executables it produced for me.
The optimised release binary isn't the issue - it's the many GB of build artifacts produced along the way if you have a lot of dependencies. You can accumulate hundreds of GB in target/ over time working on large projects.
I know this isn't your point but this is exactly why I don't use docker--but I'm a bit surprised to hear you mention `cargo build` as something that might fill up the disk. I've been a vocal critic of Rust on Hacker News in the past, but the one thing I always thought they did very, very well, was Cargo and the tight executables it produced for me.