user input should take absolute precedence

These and other silly “100% CPU” problems should not happen, first of all:

1. Mac OS X doesn’t know how to stop looping the CrashReporter process on repeated crashing apps.
2. 64-bit Linux kernel doesn’t know how to deal with full swap situation.

But more importantly, given that “100% CPU” situations will arise, why are OS’s designed in such a way that basic user inputs like mouse and keyboard aren’t given precedence at all times? Even just to catch some escape key combo to give the user a chance to correct the offending situation? I don’t believe for a moment that a small amount of computing time cannot be devoted solely to process user input at all times. If your computing resources cannot handle that, then cut out the other crap that’s going on. If the user wants to do something, listen to the user! Simple concept.

Toyota recall

So Toyota thinks it has a drive-by-wire software bug now.

And it is just now installing the “smart gas pedal.” What is the “smart gas pedal” and what’s “smart” about it, you ask? Watch…

Smart Gas Pedals May Solve Floor-Mat Problem

By Christopher Jensen

Some automakers – primarily European — are using an unusual method to reduce the chances of unintended acceleration from something like a floor mat getting tangled up with the accelerator: smart gas pedals.

If the vehicle is moving and both the gas and brake pedal are being pushed at the same time the computer tells the engine to ignore the gas pedal.

“It is an additional safety feature,” said Thomas Plucinsky, a BMW spokesman. “The brake takes precedence.”

Oh, really, the brake takes precedence. Wow.

I thought it was obvious and necessary that the design of any system with safety concerns should produce a safe outcome in the “failure” state rather than an unspecified outcome. Guess I was wrong.