Leaving your memory with no use at all would be the bug. It is a free resource that could be used to improve system performance at basically no cost (the disk is already read, the memory is still available immediately for any app that request it, etc), so it is a good default to let linux do it.

But could be cases where it could be side effects of it (i.e. running in a VM could make less memory available for the host, and it could be caching disk already) so you could consider to disable it sometimes.

No. Well, not technically... There is a UX bug in Linux. Not the only one at that, but they don't count much in Linux-land.

Just a difference in semantics -- I mean, c'mon UX in a utility like top? which is probably specified in some Unix convention anyway. Pure BSD Unix do this as well in their own way.

Free is used, black is white, truth is a lie, lie is a truth.

it confuses users. its a bug. thank you for the -4 points... :)