Stop means “stop” and Eject means “eject”
Saturday, December 1st, 2007
(photo credit - jonbro)
I can get angry. Angry at a major lack of innovation in the computer industry. Sure, we have our terabyte hard drives, 100″ screens, and quad core CPUs, but still our operating systems and hardware fail to respond to simple commands in a timely manner. I’m talking about stopping and ejecting when the computer is confused.
It’s happened to everyone. You’ve put a scratched up CD in the drive, and the CD drive decides to whir the disc around at high speed to figure out what’s up. All fine so far. Then you press eject and… more times than not, the drive will keep spinning the CD, freeze up the computer, and generally make your life a misery. Eject should mean.. spin down and eject that disc now.
Even worse is when the disc starts out okay, you begin to copy a file across from it, but then it hits trouble. Rather than being able to press the stop or cancel button and get an immediate resolution, it’s more common to have it freeze up your operating system (or at least the shell aspect of it, on the Mac Finder will freeze but other apps run okay) but still not actually “stop”.
What’s up with all of this? Make stuff happen when we tell it to happen.