Probably a bleed-over from the embedded side. Spent a lot of years working embedded control systems for NASA and DoD - bare metal systems, often interrupt driven - and it was common to have 50% margin requirements. They know those systems will grow over time, and they often have lifespans measured in decades.

Yeah, we have that with our customers sometimes. To me, an app should either be running full whack - maxing out bandwidth on CPU, disk, memory or network - or completely idle. Chuntering along at 2% is a bug. For the ones that put 'monitoring tools' that raise errors when we reach 100% on something, we set a Linux CGroup to throttle the offending resource. Takes longer, obviously, but not worth arguing with their network deployment teams 🤷 .

That RAM is mint condition collectors edition RAM. We're just storing it there temporarily.

Don't you dare fucking touch it.

My software does that anyway because I can't be arsed with multithreading or a 64 bit version

Have you used the tab groups?