OSes have done this since before Personal computers. If you write a garbage app that's being scheduled more often than it should be you'll write a garbage app t

OSes have done this since before Personal computers. If you write a garbage app that's being scheduled more often than it should be you'll write a garbage app that gets thawed out more often than it should be. All of this Android crap doesn't actually solve any real problems. On Linux, when your program blocks waiting for an event (from Xorg, its tty etc) it uses zero cpu. That's why you can leave well written apps open on a device like this. I've run out of X11 Window IDs (there's a cap in a #defined constant if you check the source) because of this. My laptop from 10 years ago had excellent suspend and the OS was very stable (I often went half a year without powering it off.) Since I have a habit of accumulating Xterm windows I would eventually open more than the limit. This never noticeably affected battery life because if they're just sitting at any sort of prompt they never get scheduled (except to redraw damaged portions of the window.)