Re:Why Is It So Hard to Detect Keyup Events on Linux?
by vardump on Sunday January 27, 2019 @02:39PM
(#19013384)
> Back in the day "RAM doublers". Because you may laugh at the idea of paying for software to pretend to increase your RAM rather than just actually buying RAM, but remember, "fix the damn problem". Nobody wants to hear about it being impossible, I want software that doubles my RAM, now write it...
Some of those products actually worked. They compressed RAM instead of paging it to disk. Which was a net benefit back then, and often still is.
Similar techniques are in use in modern Windows, macOS and Linux.
Re:Why Is It So Hard to Detect Keyup Events on Linux?
by izacus on Sunday January 27, 2019 @03:30PM
(#19013608)
> Back in the day "RAM doublers". Because you may laugh at the idea of paying for software to pretend to increase your RAM rather than just actually buying RAM, but remember, "fix the damn problem".
Those RAM doublers fixed the "damn problem" so well, that the implementation of them now lives in Linux AND macOS kernel and is enabled by default on all Macs, Android phones and several other devices.
So I think the "fix the damn problems" mentality actually works.
It won't work properly, and you'll constantly be screwed over by it, but hooray, you've got "paid software" which your boss knows was able to "fix the damn problem" so there's no point even saying it can't be done, even though it can't be done - after all they paid good money, and whoever heard of a manager spending good money on a product that doesn't work...
Most of you have probably used software built to this philosophy, a lot of the middle boxes for example. Most anti-virus software. Back in the day "RAM doublers". Because you may laugh at the idea of paying for software to pretend to increase your RAM rather than just actually buying RAM, but remember, "fix the damn problem". Nobody wants to hear about it being impossible, I want software that doubles my RAM, now write it...