Now, as for using all available memory: that's exactly the reasoning that causes so much problems for users, and that's why after so many years of hardware upgrades our machines still feel sluggish: using all resources for your app, only because they happen to be free at that moment, is not OK.
First of all, they are free now, but they might not be a moment later (because another brilliant app author has the same idea and tries to allocate everything). Second, the resources should be used in a reasonable way. If a piece software doing extremely simple computation is suddenly allocating a few gigs of RAM and takes over all cores, my thought isn't "Oh, what an efficient app, it's using all these resources I don't need", but I wonder what went wrong! What is perfectly OK for, say, a 3D rendering node, is completely wrong for an app that could do the same thing with 10x lower resource usage.
I'm not sure if I am able to explain it in more clear terms.
The thing is native apps can do that, and more in less memory. The baseline here is set by "how much is needed", not "how much memory is available".
>Is it good if a company employs a 100 people but only 15 of them do work and the rest is idle?
Yes, if 15 can do the job. then rest can moved for other profitable purposes, or laid off.
Is it good if a company employs a 100 people but only 15 of them do work and the rest is idle?