Add much as I'd like to be more efficient, modern toolchains absolutely need these kinds of numbers for big projects. My 48GB system will OOM trying to link clang unless I'm extremely careful. The 64GB system is a bit more forgiving, but I still have to go for lunch while it's working.

Sure, might be ambitious to do that sort of workload on a budget conscious laptop, but it'd be nice y'know?

▲

jshen 7 hours ago | parent | next [-]

If you're trying to link clang, this laptop is not for you. It's for people that would consider a chromebook for their use case.

▲

prmph 7 hours ago | parent | prev [-]

Usually the problem then is more fundamental.

Rust exists. If you insist on using (or need to use) languages with horrendous build architectures like C++, then you probably need a proper build server then anyways.

I don't have XCode on my Macbook and have resolved not to do iOS development any time soon (although ideally I'd have wanted to dabble in it sometimes), because I've accepted I don't want to run the rat race of always needing beefier and beefier machines to keep up with Apple's bad habit of bloating it up for each version up for no good reason.

I don't run local LLMs on my machine, since even with 100s of GB of RAM, I hear the performance you can expect is abysmal.

I think it is a good idea to put pressure on hardware and software vendors to make their products more efficient.

	▲	AlotOfReading 6 hours ago \| parent [-]
		Rust has similar issues with memory usage during linking as C++. I can use a build server when I want one, but that's not always appropriate. Local builds are useful.